Skip to main content

Start Here

Purpose​

This wiki is a small internal execution manual inside a broader Office-governed operating system. It helps Ops run nominated work with low re-entry friction once governance has compiled and prepared what matters.

Scope boundary​

This wiki documents execution doctrine. It does not own live operational state.

  • Office owns the operational Front Registry, Carry State, selection, preparation, escalation, and compile outputs.
  • Ops owns execution discipline: blocks, modes, evidence, stop rules, closure, next touch, and re-entry.
  • The GitHub projects control plane owns repository identity, lifecycle, topology, readiness, and repository-estate governance. A repository is not the same object as an operational front.
  • Weekly governance documentation may route a human toward state, but does not become a competing state store.

What this system is​

  • A loop that turns Office-nominated fronts and lightweight work units into computable progress with evidence
  • A block based day clock that selects a single mode per block
  • A verification culture: progress counts only when evidence exists
  • The execution layer fed by Office governance, not the only operational loop

What this system is not​

  • A place to brainstorm endlessly
  • A place to store every thought
  • A replacement for doing the work
  • The top-level daily governance layer (that role belongs to Office)
  • The canonical Front Registry or Carry State
  • The GitHub repository registry or repository-health authority

How to use the wiki in 60 seconds​

  1. If Office artifacts exist, start with Office Charter, and accepted compile outputs
  2. Read Ops under Office for execution posture and handoff rules
  3. Run BOOT + Daily Compiler Lite in Day Clock and Selection on the nominated subset
  4. Execute first focus block, produce evidence, and return closure outputs for Office reingest

Fallback/manual path: if Office artifacts are missing or intentionally bypassed, run direct BOOT + compiler from frontier/cadence inputs. Treat this as temporary execution recovery, not as a transfer of canonical front or carry authority into Ops.

Jump​

See also​