Sourced build record

What the work
made possible.

Sophia is built through the same persistent state, coordination and code-research machinery it gives other agents. This page leads with the resulting abilities. The exhaustive chronology, failures and review history remain available in the archive.

See what changed Open the complete archive

Repository-derived snapshot

A product under sustained dogfood.

These figures describe the product repository at a pinned revision. They are evidence of scale and testing effort—not a substitute for product outcomes.

Commits
2,900
Development days
113
Source lines
554,992
Test share
43%

Read from origin/main @ 6af3dad1 on .

Ability ledger

Engineering work, translated into product power.

“Landed” describes repository state. “Active” means the machinery is still being exercised, corrected or graduated through dogfood.

01 active

The substrate — a daemon that earns the right to be restarted

An owner can stop, upgrade or lose the daemon without planning around it: Sophia comes back serving in seconds rather than in proportion to how much she knows, verifies her own integrity while already answering, survives her heaviest background work under a strict external watchdog, and a crash leaves the data safe behind a tamper-evident journal with a governed path back to writes.

4 of 7 waves landed · now: Serving through the heaviest check

Inspect the full arc
02 active

Governed context delivery — what the substrate was for

An agent can ask a declared question and receive a compiled fact bundle instead of a search result: every fact bound to its supporting records, provenance and authority preserved, corrections and contradictions surfaced rather than flattened, deterministic graph operations computed exactly instead of guessed — with a statement of whether the evidence is complete, and a receipt recording exactly what the model was given before it made a claim. No ordinary retrieval stack can honestly issue those receipts: they exist only because the state layer underneath is journaled, verified and supersession-aware.

0 of 4 gates landed · now: A bounded experiment first

Inspect the full arc
03 active

Verified retrieval — a code graph that refuses to bluff

An agent can ask what a codebase does and receive an inspectable path through exact symbols, source sites and resolved edges — or a precise instruction to open source when the graph cannot prove the answer, never a plausible story disguised as structure.

7 of 9 milestones landed · now: Prove the graph before anything compiles from it

Inspect the full arc
04 active

Workspace identity — agents become durable, governed participants

An owner can run many agents as stable seats inside durable workspaces: identity survives credential rotation and daemon restarts, authority stays scoped to the workspace, and explicit handoffs carry the work across fresh connections without pretending the new process remembers the old one.

6 of 7 phases landed · now: The owner drives it for real

Inspect the full arc
05 active

The owner’s window — a UI that is not allowed to lie

The owner can see what the system knows, what the fleet is doing and where intervention is required — then curate, retire or govern it without translating raw protocol objects or trusting invented status.

5 of 6 units landed · now: Every runtime state gets a surface

Inspect the full arc
06 active

The coordination ledger — the fleet stops reconstructing the truth from chat

Agents can act on one causally ordered state of the work: stale writers lose, terminal outcomes stay terminal, and “what is true now?” no longer depends on interpreting the latest sentence in chat.

9 of 10 waves landed · now: Posts become commentary

Inspect the full arc
07 active

Sophia Superpowers — governed operating methods for every agent

Sophia can give every supported agent the same reviewed operating method, reject workflows that exceed their declared capability, verify a matching installed release at session start, and expose drift or missing activation without letting a skill widen the agent’s authority.

9 of 10 waves landed · now: The remaining chain-of-custody boundary

Inspect the full arc

Recent record

The last six consequential turns.

Features and failures share one record because production truth is part of the product.

  1. feature

    The graph answers bounded questions, with receipts

    Code-graph retrieval grows up into a product surface: structural queries return bounded answers under complete checkout authority, each carrying the receipts that name exactly what was consulted — and a dogfood matrix, not a demo, decides what may ship.

  2. feature

    Identity gets a trusted presence

    The dependency the workspace-identity arc refused to fake gets built: a Linux trusted-presence provider with frozen, cross-language-proven protocol bytes, managed agent launches from the CLI and a native tray through owner-approved terminals — and browser executable authority removed outright rather than grandfathered in.

  3. dogfood

    2,028 of 2,028

    The code-graph witness backlog — livelocked for weeks under the system’s own background pressure — converges after the resync fairness fixes: every frozen witness re-measured, zero remaining. The truth surfaces held end to end, and the fairness gap that remains is ticketed by name instead of rounded away.

  4. feature

    READY before the seal verifies

    The restart architecture merges: the daemon serves first and verifies its own integrity after, holding writes in a published, bounded window instead of holding the door. Every phase of startup is timed into one record, and a real boot that misses the budget fails the test suite rather than a dashboard.

  5. trust moment

    The restart bill arrives

    A guarded restart on real state reads the whole database and takes seventy-five minutes to come back — and the watchdog meant to catch a wedged daemon causes an outage of its own. The ruling lands the same day: restart cost may never scale with database size again. Write-ahead logging plus a background snapshot, under a thirty-second budget.

  6. trust moment

    Production-scale dogfood hardens graph reads

    A production-corpus overview exposed an unbounded proof-replay path before the graph graduated from dogfood. We replaced it with a bounded control-plane projection: the same overview returned in 359ms, four concurrent graph reads finished in 564ms, and the daemon remained stable. Resource budgets and worktree-identity safeguards remain explicit graduation gates.

How this record earns trust

The page loses when it disagrees with the repository.

01

Numbers are derived

Repository statistics are generated from a named revision, never typed into the page as floating claims.

02

States are anchored

A unit can only present as landed when its commit is resolved against the tracked main branch.

03

Failures remain visible

Dogfood incidents and corrections stay beside the feature work instead of being polished out of the story.

The complete record

Every milestone, active arc, review rail and correction remains available.

Enter the development archive