Projects, owners, deliverables, blockers and the reporting rhythm — the office is the board
Every project has an owner seat, deliverables with a fiscal-week target and acceptance criteria a script or a named seat can verify, and blockers with a date. The board is the office's replacement for a task tool: it renders from governance/projects.json, and verify_projects refuses an owner that is not a seat, a dependency that does not resolve, an active deliverable with no acceptance, or a blocker with no date. Today is 2026-W34 (2026-09-07).
14projects
52deliverables
11accepted
0slipped
18unscheduled
10open blockers
5active
5blocked
4planned
Open blockers, oldest first
23 working days · owner Executive ChairmanRotate every leaked key, purge the history, push, and let the gates run on every change Eleven live keys have been in git history since the initial commit; rotation is the operator's and has been owed since 2026-08-05. The December open-source release depends on this. since 2026-08-05 · resolves when: verify_key_rotation passes with every owed key attested revoked.
21 working days · owner Executive ChairmanFinessionals on air: the rig, the rehearsal, the first Sunday Two operator decisions (graphics-server key test; disk 29.2 vs 33 GB per episode; Studio Mode) have been waiting on the Chairman since the rig was certified. since 2026-08-09 · resolves when: The three answers are recorded on the producer runbook.
10 working days · owner Executive ChairmanThe front door, office-native: forms, scheduling, landing pages and the CRM they write into — Typeform, Cal.com and Airtable retired The GTM page still says the free consultation runs 'through end of Q2' — that window has passed; the free/paid rule for the consult needs a current date. since 2026-08-24 · resolves when: scheduling.json consult-60 carries the rule and the GTM page reads it.
10 working days · owner Executive ChairmanThe proving ground: run one brand with one developer and one creative, autonomously — then scale toward six brands in thirteen weeks The Executive Director seat is in the sandbox barter and the candidate has asked for a defined, compensated engagement before scaling commitment — the seat's terms (fixed paid role from October or not) are undecided. since 2026-08-24 · resolves when: The Chairman decides the seat's October terms and the executive schedule is drafted for counsel.
10 working days · owner Executive ChairmanTake the consent + intent layer to market: six buyers in order, one data model, the source rules The co-chairman/CTO package describes scraping and compiled databases across 43 verticals; the playbook's positioning is public-and-consented data only. No campaign can be placed for that seat until one of them changes. since 2026-08-24 · resolves when: A decision is recorded on the CTO/co-chairman role page and in gtm.yaml.
10 working days · owner Executive ChairmanCounsel review: five agreement contexts, the two-phase model, and the executive and producer schedules Counsel has not been engaged on the v2 documents. since 2026-08-24 · resolves when: COUNSEL-REVIEW.md carries a reviewed date and the doc_version loses its -draft suffix.
10 working days · owner Executive ChairmanThe Community Incubator: a seat, a page, and a growth plan No seat exists for the Executive Assistant / Incubator owner, so the project cannot be owned by anyone but the Chairman. since 2026-08-24 · resolves when: The seat is added to roles.json.
10 working days · owner Executive ChairmanOutbound in the office: the warm sequences, the GO gate and the consent guard on the one record — Airtable frozen as an archive The GO gate is closed: nothing sends until the Chairman sets outbound_policy.go_opened_at and policy.json outbound.go after the re-consent draft is reviewed since 2026-08-24 · resolves when: GO opens 2026-09-13 (2026W37): the Chairman sets outbound_policy.go_opened_at after the ED reviews the re-consent copy
10 working days · owner Executive ChairmanOutbound in the office: the warm sequences, the GO gate and the consent guard on the one record — Airtable frozen as an archive The migration 20260830_outbound.sql is written, not applied (the Chairman applies migrations) since 2026-08-24 · resolves when: the migration is applied after 20260828_workspace_members.sql
10 working days · owner Executive ChairmanOutbound in the office: the warm sequences, the GO gate and the consent guard on the one record — Airtable frozen as an archive The Airtable Contacts CSV export (with a Record ID column) has not been provided since 2026-08-24 · resolves when: the export is in the private import folder and import_airtable_archive --live has run
Projects
blockedThe Community Incubator: a seat, a page, and a growth plan
An office page for the Incubator rendered from data: what it is, who it is for, how someone anywhere joins p-community-incubator:d2 · depends on p-community-incubator:d1
unscheduled
artifact https://office.temerarii.xyz/incubator/
blockedCounsel review: five agreement contexts, the two-phase model, and the executive and producer schedules
Nobody appears on camera and no engagement is formal until counsel has read the words. It is the longest-lead item on the board.
Status
Deliverable
Target
Accepted when
blocked
The five contexts (finessionals, studio, collaborator, executive, producer_partner) at doc 2026-08-tmr-2-draft reviewed and cleared p-counsel-review:d1
The executive schedule: Executive Director scope, authority, commitment, compensation or revenue share, payment schedule, termination — as a signed schedule, never a page p-counsel-review:d2
Code review before deploy (Samuel's g) has no gate behind it until the repository can be pushed, and it cannot be pushed while live credentials sit in its first commit.
Status
Deliverable
Target
Accepted when
blocked
Database password and both Supabase keys rotated (they were pasted in a session on 2026-08-24) p-credential-purge-ci:d1
Outbound ran on a cron against a CRM the office could not see, with no consent receipt and no clock. The Chairman's decisions put it on the one record, the one calendar and the one policy; nothing sends until GO.
Registry + calendar lane + /outbound page: sequences derived from funnel.yaml, steps as fiscal-week cells, the GO gate as a dated blocker — v2 (stages × capacity) p-outbound:d3
Stages: score_intent · assign_segment · plan_outbound (every candidate through can_send) · draft_touches (rails, caps, no studio name) · pull_metrics_outbound p-outbound:d4 · depends on p-outbound:d1
2026-W36 (2026-09-06)
gate engine/gates/verify_outbound.py#OUTBOUND PASS review by Executive Director(human-judged)
planned
Re-consent form (email + versioned consent) in forms.json; the one re-consent send drafted and reviewed p-outbound:d5 · depends on p-outbound:d2
2026-W36 (2026-09-06)
gate engine/gates/verify_intake.py#INTAKE PASS review by Executive Director(human-judged)
planned
The lane promoted onto the calendar: GOAL.yaml campaign, loaders keyed by campaign, content index emits outbound cells with cuts p-outbound:d6 · depends on p-outbound:d3
claw's cron reads drafts from crm_touches, re-checks can_send, records sent/replied/bounced through outbound_store; the Airtable sync retired p-outbound:d7 · depends on p-outbound:d4
activeThe contact graph: one record from the door to the deal — every Typeform question and Airtable column typed into Postgres, the archive imported unsendable, parity proven by a gate
The Chairman exported the Sales CRM and asked that nothing be lost in translation. One record with consent at the root, accounts, opportunities, tasks and the legacy sequences held — and a gate that says every column landed.
All 8 CSVs imported --live: 147/16/9/7/1/9/7 accounted, receipt null on every row, legacy sequences held and never resumed p-contact-graph:d3 · depends on p-contact-graph:d1
2026-W35 (2026-08-30)
gate engine/gates/verify_crm_parity.py#CRM-PARITY PASS review by Executive Director(human-judged)
done
segment_rules.json confirmed by the Chairman (5 buckets × need → 13 segments) and read by assign_segment — confirmed 2026-08-25 p-contact-graph:d4
Every CTA in the GTM strategy pointed at a third-party tool with its own data model. One record with consent at the root, written by our own forms and scheduler, is the consent layer applied to ourselves.
Status
Deliverable
Target
Accepted when
done
Forms rendered from forms.json (inquiry derived from the Typeform definition + three short forms), consent versioned, logic as show_if p-front-door:d1
Typeform (3 forms, every response) and Airtable (Sales CRM) exported to a private import folder and imported with consent = null (unsendable until a receipt exists) p-front-door:d5 · depends on p-front-door:d4
The office had the strategy half of management (objectives, pipelines, gates, sign-off) and none of the tracking half. The Chairman cannot step away from what nobody else can see.
Status
Deliverable
Target
Accepted when
done
Projects registry + /finessionals/board rendered from it p-office-pm:d1
EOD / standup write surface: a per-seat report link, no login, recorded in Postgres p-office-pm:d2
2026-W34 (2026-08-23)
artifact https://office.temerarii.xyz/report/ review by Executive Director(human-judged)
planned
eod_report becomes machine-observed: the emitter reads filed reports and the board shows compliance per seat p-office-pm:d3 · depends on p-office-pm:d2
The Chairman's stated condition for paid client work and for stepping away: watch the Executive Director take a dev and a creative and run a brand without him.
Targets are PROPOSED from 'up to six within thirteen weeks' counted from this week (2026W34 → W47). The Executive Director confirms or re-dates them; a re-date is a commit.
Status
Deliverable
Target
Accepted when
planned
Brand one stood up through the any-brand intake: a quarter of content generated, calendar placed, office rendered p-ed-proving-brand:d1
2026-W36 (2026-09-06)
gate engine/gates/verify_gtm_to_calendar.py#CHAIN PASS review by Executive Manager(human-judged)
planned
Brand one's first week certified and published with the developer and creative working the cockpit, the ED signing off p-ed-proving-brand:d2 · depends on p-ed-proving-brand:d1
2026-W37 (2026-09-13)
gate engine/gates/verify_unified_matrix.py#UNIFIED-MATRIX PASS review by Executive Director(human-judged)
planned
Six brands running on the same engine, each with a named EM, dev and creative p-ed-proving-brand:d3 · depends on p-ed-proving-brand:d2
EOD reports filed from the team channel land in the same table as the report form p-multiplayer-agent:d2 · depends on p-office-pm:d2, p-multiplayer-agent:d1
Stated once, here. The EOD form, the policy page and the scoreboard read the same fields and the same cutoff, so a report cannot be filed against one definition and scored against another.
Rhythm
Cadence
Fields / reads
Who
Notes
standup
every working day
yesterday, today, blockers
every active seat; the Executive Director runs it
the EOD form doubles as the standup record — a standup is yesterday's EOD read aloud
18:00 America/Chicago — every seat, recorded in UTC (the Chairman, 2026-08-25) · before the next standup · eod_report (governance/scoring.json) — machine-observed once the emitter reads the filed reports
weekly review
Friday
every deliverable due this week and its acceptance, every blocker older than three working days, the EOD compliance count per seat
executive-director with the Chairman
next week's priorities on this registry — a change here is a commit, so the decision has a diff and a date
Latest end-of-day report, per seat
No reports pulled yet. Reports are filed on a per-seat link (/report/<token>), stored in Postgres, and folded into the office by python -m engine.stages.pull_eod_reports before a build. Until the first pull, this section is empty and says so rather than showing a report nobody filed.
