FIFTY.DEV
All workWork /IGRIS
01 / 08 — CASE STUDY
CONCEPT VISUAL · GENERATED
StatusActive · source snapshot
Year2026
RoleAuthor · Architect · Sole Engineer
StackTypeScript · Node · SQLite · MCP
Duration2025 → ongoing
TypePersonal · open source

IGRIS

An engineering OS for AI coding agents. Durable work state, explicit ownership, and one brain beyond the conversation.

THE WORK

// 01 · PROBLEM · APPROACH · OUTCOME
01// PROBLEM

The session ends. The work does not.

Usage limits, crashes and tool switches leave the next session reconstructing decisions, failed checks and ownership. A transcript is not a handoff.

IGRIS keeps the brief, owner and stopping point outside the model. The repository documents a same-machine Claude → Codex handoff; it is a demonstration, not a measured recovery rate.

02// APPROACH

State first. Constraints at the boundary.

A local SQLite brain stores briefs, claims, sessions and knowledge. MCP and harness adapters project that state into the tools around the model. Project standards and the working tree remain separate authorities.

Hooks enforce workflow checks on supported harnesses; Codex, Gemini CLI and Cursor use advisory bridges. Local atomic claims prevent duplicate local ownership, not cross-machine conflicts.

03// OUTCOME

An inspectable system, not a black box.

Seven cognition extractors turn transcripts and brain records into candidate knowledge. Review is the default for semantic changes; optional automatic actions and deterministic hygiene are explicit exceptions.

The dashboard exposes graph, search, triage and diagnostics. This source snapshot includes working-tree hardening, not a published release or a fresh test run. Cross-machine handoff and phase resume still need stronger evidence.

ARCHITECTURE

// 02 · DURABLE STATE · REVIEW PATH
IGRIS durable architecture. operator and descriptor-driven adapters feed coding harnesses with supported-hook and advisory tiers. harness and CLI requests reach the MCP gateway, component handlers and local brain store; handlers also emit events. a separate context-to-role-to-constraint path reaches the working tree and Git. a note qualifies workflow enforcement as not a security boundary.Open full-resolution image (new tab) ↗
generated architecture slice, not a product screenshot or a map of every read and write. descriptor-driven adapters project to supported harness surfaces; runtime requests instead enter the MCP gateway and component handlers for local state access. those gateway, handler and store labels identify the same boundaries in the cognition figure, not a second brain. the two harness tiers and their names are explained in the adjoining workflow prose. configured roles and supported gates are not a security perimeter: exemptions, bypasses and fail-soft paths remain. component events feed cache projection, monitoring and sync listeners outside this slice. optional personal-brain replication is asynchronous, not consensus; checked export/import bundles are a distinct mechanism. neither replication nor bundles is drawn here. the host-dependent scheduler and trusted shell dispatch remain outside this figure too. source snapshot: 2026-09-06; inspected implementation, not a release or performance result. [N04, D01–D05, D10–D16, K15, K16]
IGRIS default cognition review path. local brain records and transcripts feed a shared host, then pending learnings and suggestions reach operator review through the local dashboard. a chosen mapped apply action returns through the MCP gateway and component handlers to the same store. handlers also associate supported maintenance with pre-state, undo and audit. notes preserve automatic-action and hygiene exceptions and fail-soft undo capture.Open full-resolution image (new tab) ↗
generated default semantic-change path, not a product screenshot or a map of all mutations. brain records and transcripts feed one shared cognition host; validated candidates enter pending queues, not approved knowledge. an operator reviews through the local dashboard and may reject, dismiss or choose a supported mapped apply action. the action reaches the MCP gateway and component handlers before memory or graph changes persist. gateway, handler and store labels refer to the same boundaries in the durable architecture figure. pure database readers separately support dashboard inspection and opening record detail; the queue-to-review arrow describes a human interaction, not a requirement to read through the apply gateway. optional automatic actions and deterministic hygiene are exceptions to default review, not hidden bypass arrows in this slice. supported maintenance carries pre-state, undo and audit accompaniment, but capture can fail softly and recovery is not guaranteed. enablement, budget, timeout and process-isolation limits remain in the accompanying prose; isolation is not a kernel security sandbox. source snapshot: 2026-09-06; inspected implementation, not execution or accuracy evidence. [C01–C07, K01, K02, K06, K07, U05]

STACK

// 03 · WHAT IT'S MADE OF
CoreTypeScript · Node
PersistenceLocal SQLite · guarded disk cache
GatewayMCP · component handlers
RetrievalBM25 + vectors · rank fusion
GraphTyped entities · qualified edges
CommunitiesLouvain · cluster pass default off
CognitionShared host · isolated subprocesses
HarnessesAdapters · capability-specific gates
PortabilityChecked bundles · optional replication

PROCESS

// 04 · INSPECT THE WORK
IGRIS cognition diagnostics list perception, subconscious, synapse, janitor, arbiter, curator and cartographer. the cartographer row has a yellow NO SIGNAL warning; other rows show terminal event and queue details. the hostname and database-path footer are outside the crop.Open full-resolution image (new tab) ↗
genuine local diagnostics, captured 2026-09-06. the registered extractor roster shows run evidence, schedules and queue populations. cartographer remains NO SIGNAL: the retained local event window is silent, while an other-host observation is separate. these states are a snapshot, not extractor accuracy or proof that every job ran here.
the IGRIS whole-brain graph displays a large circular field of pale nodes with dense central clusters and connecting lines. the scope is whole brain, the refresh control is visible, and the inspector says nothing selected. individual record labels are not visible.Open full-resolution image (new tab) ↗
genuine whole-brain graph, captured 2026-09-06 with all projects and entity types unfiltered. native pan and zoom expose the dense topology with nothing selected. counts belong to this snapshot, not a benchmark. the query freshness footer is outside the viewport; this image does not certify an exact query time or record-level readability.
three IGRIS overview cards show brief states, priorities and instances, with the igris-ai scope label above. the private project registry and graph scale card are cropped out.Open full-resolution image (new tab) ↗
genuine overview detail for the igris-ai scope, captured 2026-09-06. brief states, priorities and instance records describe this local snapshot. these counts do not establish delivery speed, recovery quality, active-process liveness or a permanent project total.

NUMBERS

// 05 · AUDITED SCOPE · NOT PERFORMANCE
// Feature evidence
57
source-mapped rows · not 57 shipped claims
// Cognition extractors
7
bounded jobs · one execution host
// Dashboard routes
6
overview · graph · layers · triage · search · diagnostics
// Frontier entries
7
working-tree, experimental or deferred scope

LESSONS

// 06 · WHAT TO TAKE FORWARD
01

State survives a change of model.

Persist the job card, ownership and last inspection result. A new context window should resume work, not reconstruct a conversation.

02

Name the enforcement boundary.

Hooks and advisory bridges are not equivalent. Workflow checks have exemptions and bypasses; they are not a security perimeter or distributed consensus.

03

Show inference before calling it knowledge.

Review defaults, provenance and maintenance history make proposals inspectable. Optional auto-apply needs separate judgment; process isolation is not a kernel sandbox.

04

Earn the next claim.

The audit inspected source and test definitions, not fresh test results. Dashboard captures came from an existing bundle. Repeatable phase resume and cross-machine handoff remain evidence to earn.

BUILDING AGENT SYSTEMS?

Inspect how the work survives the session. Read the handoff note, explore the evidence, or compare notes on engineering systems.

FIFTY.DEV●WORK · IGRIS●DURABLE STATE●ENGINEERING OS●FIFTY.DEV●WORK · IGRIS●DURABLE STATE●ENGINEERING OS●