Organization Architecture — Implementation board

Organization architecture · Organization Core. Names updated September 16 to match the existing ORG# boundary. “Portfolio” means a collection of properties. Earlier recordings and quotations retain their wording; existing links and technical IDs remain stable.

Exhaustive reconciliation · 16 September 2026

All accessible text in 100 threads / 1,918 messages was reviewed through the 07:02:55 UTC snapshot, including an older active thread. The 07:31:45 UTC refresh of 99 recent roots found no new or changed content. All 344 current board rows, the deck, HOW tabs, podcast text and 166 attachment records were accounted for. Three deleted raw chunks remain unavailable; videos were reviewed through extracted transcripts where available and sampled frames, with legibility limits. This is context reconciliation, not a certification of every deployed feature.

The same-phase source-identity correction and amended dropdowns carry the work. Completed receipts and earlier decisions remain historical. Read the current strategy, ALIGN1–16 before following an older example.

Current strategy · 16 September 2026

Current direction: roles describe and route work; they do not restrict ordinary in-scope reads or edits. Explicit org/property entitlements, provider consent, value locks and validation remain. Admin—including Dev Tools and Atlas—is restricted to the three explicitly assigned platform administrators: Sean, Fede and Gera. Earlier delegated-role privilege machinery below is historical/future design, not launch acceptance.

Current direction: the backend queries authorized org/property scope intersected with this tab’s selected scope. It must not load every property’s business rows and filter them in the browser. Use the explicit URL selection with tab-local restoration; a shared mutable selection cookie cannot synchronize all tabs. Background sync and durable workflows retain their own authorized operation scope.

Review basis and source precedence

Transcript snapshot: 27 August–16 September 2026, captured 2026-09-16T06:04:57.783208+00:00. Inventory: 98 threads, 1,821 messages; architecture-bearing raw discussions and replies were reviewed alongside recaps, the September 1 industry interview canvas, design chapters and linked podcast/settings sources. This is not a claim to have re-adjudicated every historical stress case. The interview’s speaker labels were reconstructed. Current direct founder clarification overrides older proposals; later explicit decisions outrank earlier interpretations. Original recordings, completed-row evidence and unrelated driver updates are preserved.

Implementation map: nine linked adjustments remain in their original phases; existing completion evidence stays historical. The dropdowns explain the decision, deliverable and acceptance. No implementation is certified by this planning update.

Current strategy and source precedence →

Last check: reading… · last change: —

End to end, grouped by phase — the eleven ladder phases (83–121 engineer-days) and the fifteen UI phases beside them (≈48–53), through to the road items. The current item count is derived below. Completion follows each item’s current acceptance and evidence.

Read this first. Grouped by phase, in the ladder’s own order, so the top of the page is where we actually are. Two tracks, and they are priced separately on purpose: the eleven ladder phases P00–P9 are the data work (83–121 engineer-days, of which 50–73 committed); the three UI lanes — switcher, dashboard, atlas — are fifteen phases beside the ladder, not on it (≈48–53 days), and they run in parallel once S-A’s contract lands. A phase opens only when the last one’s test is green. P00’s execution detail IS here — its 49 rows sit under Phase 00 beside the phase’s own summary row, each one carrying its real PRs, so this page derives their status from live PR state exactly as the operator migration kickoff does; the two cannot disagree, because they read the same source. New operator-migration rows are still authored on the kickoff page — this one mirrors it. Voice rows (ids v0-…, v3-…, v6-…, v9-…) are the shared phone agent riding this ladder; their pictures are on /a/voice-merge-surgery-2026-09-09 §0.1–0.2. The voice slice is built now, on Gera's shapes, with placeholders that a drift test retires when his module lands.

Status on this page is AUTHORED, not derived, and that is a property of the subject rather than a shortcut: a phase is not a pull request, so bin/refresh-tracker has nothing to read on these action items. What makes it checkable instead is that every item names its exit test — a named fitness function, not a judgement call — so you can ask whether that test passes rather than whether someone remembered to update a word. The execution detail underneath each phase does derive, on its own pages, and the action items link to them. Last edited 2026-10-15 07:49Z.

The ladder at a glance

Eleven phases, sixteen steps, 83–121 engineer-days, of which 50–73 are committed — plus fifteen UI phases beside the ladder at ≈48–53 days. The rail is working days from Tue Sep 15. Each phase opens only when the last one’s test is green — the exit column is that test, a named fitness function rather than a judgement call.

Phase	Who	Size	Lands	Green when
P00 · vocabulary	Gera · Astra	not priced	ahead of P0	the ratchet holds while the person-sense identifiers are gone
P0 · week 1	Fede · Gera	W0	Sep 8–12	the Western Slope leasing line answers, counted
P1 · the org row	Gera	5–7 d	Sep 21 / 23	`roster-stamp-complete`
P2 · the bench	Fede · Gera	4–6 d	by Fri Sep 26	the harness can say GREEN — `expect:'GREEN'` + `closesAt`
P3 · rows, dark	Gera	7–10 d	Oct 7 / 15	`second-claim-refused-by-store`
P4 · the resolver	Gera	4–5 d	Oct 13 / 23	byte-equal on the first two keys
P5 · the wall	Gera + many hands	14–21 d	Nov 2 / 23	the isolation gauntlet T1–T19 — the observe→refuse flip
P6 · shared line	Fede · Gera	12–18 d	Nov 18 / Dec 17	`same-agent-id-every-line`
P7 · owners, login	Gera · Fede	7–10 d	Nov 24 / Dec 25	the switcher lists memberships
P8 · vendors	Gera	≈10–13 d	beside the ladder	`vendor-roster-parity`
P9 · the road	Gera · hands · Fede	30–44 d	Jan 8 / Mar 3	one fitness function per step
Beside the ladder — the UI, three lanes in parallel once S-A lands (≈48–53 d)
switcher · S-A…S-F	Fede · Gera	17–21 d	S-A gates all three	zero unstamped buildings, and the org reader agreeing with the seeder
dashboard · D0…D4	Fede · Gera	17–18 d	after S-A	a query from the wrong org returns zero (ST-46)
atlas · ATL-A…E	Gera · Fede	14 d	ATL-D waits on the record	`map-dump-stable`; the projector snapshot on bench fixtures
The demo Gera described — switcher, multi-select, a set-aware dashboard — is S-A → S-B → DB-D1 → DB-D2, about 16–19 days against the 14 working days to Fri Oct 2, so it fits only if S-B and DB-D1 overlap. The sweeps do not fit the frame.

Decided without stopping — every call taken so we could keep building

The operating rule: a decision that looks like Gera’s goes to Astra first, then Fable 5.1, and reaches Gera only if both decline — and the loop carries on with any phase that does not depend on it. Nothing below stopped the work. Each was taken from the recorded rulings rather than parking the phase, each is a model decision under delegated authority and NOT a founder ruling, and each names what it forecloses so it can be reversed by reading one paragraph. This section exists so that disagreeing later is cheap. If one of these is wrong, say so and we change it — the cost is a sweep, not a restart.

The call	What was taken	What it rules out
The two fleet roles P00 · note	`fleet engineer` for the human driving our fleet, `fleet agent` for the unattended software role. Neither creates an authorization role.	Keeping an internal human or AI meaning of `operator`; treating every internal occurrence as `staff`; calling the unattended writer an engineer.
Clara’s public title P00 · note	“Your AI Teammate.” Clara keeps her name; the word `operator` is freed for the customer’s company.	Retaining “AI Operator” as a secondary title or a settings alias. Marketing copy and its visual expectations need updating.
The handover mechanism P00 · note	`ADMIN_HANDOFF`. One mechanism for both a stand-in handover and a plain change of managers.	`TRANSFER` — it collides with the voice lane’s live call-transfer meaning, and its bigger occurrence count reflected unswept history, not fitness.
Which keys may default P00 · note	Product behaviour may carry a PropFlow default; business and legal terms may not and resolve to an explicit unknown — finding out. Applied key by key.	A default pet fee or any term a resident could rely on. D-0910-1 ruled the layer EXISTS; it did not rule which keys may use it — this went beyond it deliberately.
`acting operator` as a role P00 · note	No — it does not survive as a named role. The company administering the account under a temporary mandate is a RELATIONSHIP, expressed through custody, billing and grants.	A third role beside `operator` and `staff`; a replacement named `custodian`. Genuine transcription keeps its own provenance and permission.
Defaults rollout P00 · note §4	Staged activation retained. This one is flagged in the note as a conditional founder choice — it picked an arm rather than parking the phase on it.	A named, audited simultaneous change across every affected live property. The likeliest thing on this table to want overturning, since the other arm buys speed for incident exposure.
What counts as shipped tracking · note	A merge link is not production evidence. 22 of 24 “shipped” rows were proved by a GitHub URL; removed, headline 24 → 2.	Treating merge evidence as production evidence; grandfathering bad entries because another page has them. A lesson-shaped row can never reach shipped.

Still genuinely open, and not silently decided: whether an archived company’s addresses are released (N6); a resident community’s own quiet hours, which is a different thing from Clara’s contact window; and the contents of the default role permissions, deferred until the features they cover land. These are recorded as open rather than answered, because inventing an answer to them would foreclose something real.

Overall

—

finished

Merged counts as done (Gera, 2026-09-11). Proven in production, plus merged work, plus work with no production surface to exercise — a decision, a doc, a test fixture.

—

proven in production

The strict count: a permalink shows the change working in production. A merged pull request does not qualify.

—

Shipped

—

No prod surface

—

Merged · untested

—

In flight

—

Open

—

Waiting on you

Groups — click to filter

Every action item opens: when it was added, why it exists, and the links that prove it. Action items waiting on a human carry a Decide → link straight to the answerable question on the decisions page. Statuses are re-derived from live PR, decision and prod-evidence state by bin/refresh-trackers; nothing here is typed by hand, and merged is not shipped until a prod_evidence permalink says the fix was exercised in production.