cyberia/projects/fathership.md

fathership

the first project of the system: to change how the system itself behaves, until dev describes what is in force and the owner is a father, not an architect. a task with sub-tasks; the sub-tasks below are its phases and the pages each phase must make true.

the measure

three numbers on the state board, weekly: the share of merges with no owner action; the time from a task becoming ready to its change merged; the verdicts brought to the owner, and how many were real ties.

phase 0 · scaffolding · 2026-10

the loop runs on repositories and GitHub; the owner writes the product pages.

sub-task status
every object of dev has a page with kind, status, owner, serves; tasks in tasks/ of the owning repository doing
the views of dev are generated from pages: the verdict queue, the role board, the state board open
the product pages of the ten rungs exist and carry dots; the counter sets the dots from audit/ open
the gates of deliver run at the three scopes; the merge of a task-scope change needs no owner open
convergence and dispatch run across the four bodies; the reviewer is always another body open
the release train covers the whole ladder doing
the 307 open pull requests are settled by the rules of deliver: merged if whole and re-verified, closed with a reason otherwise, branches kept open
the launch worker runs again as the runner of deliver blocked by the rows above

phase 1 · the graph · 2026-11 → 12

the pages are read from the cybergraph: a task is a particle, its state is signed cyberlinks, ready is a query; the seer proposes product pages and the owner accepts them. gate: one week in which every board the owner reads is rendered from the graph and agrees with the repositories.

phase 2 · the organism · 2027-01

the graph is the only record; a change travels as a patch; GitHub mirrors; M drives the seer. gate: thirty days without the scaffolding.

verdicts waiting

a query, listed here until the views are generated: review tasks of the owner with status open.

decisions

review tasks of the owner with status done, by date.

  • 2026-10-07 · GitHub issues are an inbox, pull requests the wire of a change, boards renders of the graph
  • 2026-10-07 · vendors by the class of work, never by loyalty; the reviewer is always another body
  • 2026-10-07 · the declared version bump is at least the computed one
  • 2026-10-07 · the owner's mac is the runner for metal, dmg, apk and fleet until a dedicated machine exists
  • 2026-10-07 · in phase 2 GitHub is a mirror; the wire is the patch
  • 2026-10-07 · d5: the 2025 vision page is the valley's pitch and lives in cyber valley
  • 2026-10-08 · d2: the mission sentence is "the cyberstate, led by superintelligence" everywhere
  • 2026-10-15 · landings and decks stay in the wide lane — fast now, frozen later by a decision
  • 2026-10-22 · the life-os development machine studied (development machine study): take admission by execution, capability over prose, a finite agenda on one snapshot; leave ledgers, a machine spec, the artifact zoo. expected effect: no new artifact type enters the process · check: the objects table of dev.md a month from now · outcome: —
  • 2026-10-22 · requirements pilot on the chain spec (soft3 PR, feat/requirements-chain): 45 ids, 95 cases, the map and the counter; first count 🔴 39 🟡 5 🟢 1 — 34 stale because every receipt predates 25 commits. expected effect: a fresh receipt at HEAD turns the stale rows and the counter becomes the chain's readiness number before 2026-11-05 · check: scripts/requirements.py --dots on soft3 main · outcome: —
  • 2026-10-15 · the charter is one scheme; the development process is dev and deliver; fathership is the first project, not the law

Graph