Operating contract
Rules every entering agent should respect before touching files.
Seeds
The skill writes readable files into the repo so ownership, proof, review state, and resume context survive the thread.
They are intentionally plain text. The point is not a private dashboard; it is a record any future thread or engineer can inspect.
Shared rules for every agent that enters the project.
# Project Agent Rules
- Preserve user changes. Never revert unknown work.
- Keep one active writer in the main worktree by default.
- Treat external effects as explicit operator actions.
- Record proof commands and residual risk before declaring done.
- Use the factory docs as the routing source of truth.Mode, review posture, permissions, stop rules, and verification cadence.
work_mode: balanced
user_involvement: principal_partner
concurrency_policy: single_writer
verification_level: focused_plus_build
reviewer_policy: risk_triggered
default_stop_mode: drain_to_checkpoint
external_effect_policy: explicit_operatorWhat changed, what passed, who owns the next step, and what remains risky.
## Current State
status: running
active_owner: builder-thread
current_slice: install flow and landing shell
accepted_evidence:
- npm run typecheck
- npm run build
- browser smoke on desktop and mobile
next_action: review generated asset integrationA scoped work package with enough evidence for review or resume.
## Handoff Bundle
objective:
write_scope:
non_goals:
files_changed:
proof_commands:
known_risks:
recommended_next_action:
stop_or_resume_notes:A small index of what was reviewed, accepted, deferred, or blocked.
## Review Index
| Slice | Reviewer | Result | Evidence |
| --- | --- | --- | --- |
| landing shell | reviewer-thread | accepted | build, browser smoke |
| install copy | reviewer-thread | accepted | source readback |
| mode graphics | pending | needs visual QA | desktop/mobile screenshots |Rules every entering agent should respect before touching files.
The editable settings for mode, verification, review, stop rules, and effects.
The durable record of what changed, what passed, and what remains uncertain.
The bundle that lets review or resume happen without guessing.
A small index of accepted, deferred, blocked, and pending review work.
When a thread restarts, the project record should answer where the work stands before another edit happens.
Shared rules for every agent that enters the project.
# Project Agent Rules
- Preserve user changes. Never revert unknown work.
- Keep one active writer in the main worktree by default.
- Treat external effects as explicit operator actions.
- Record proof commands and residual risk before declaring done.
- Use the factory docs as the routing source of truth.Mode, review posture, permissions, stop rules, and verification cadence.
work_mode: balanced
user_involvement: principal_partner
concurrency_policy: single_writer
verification_level: focused_plus_build
reviewer_policy: risk_triggered
default_stop_mode: drain_to_checkpoint
external_effect_policy: explicit_operatorWhat changed, what passed, who owns the next step, and what remains risky.
## Current State
status: running
active_owner: builder-thread
current_slice: install flow and landing shell
accepted_evidence:
- npm run typecheck
- npm run build
- browser smoke on desktop and mobile
next_action: review generated asset integrationA scoped work package with enough evidence for review or resume.
## Handoff Bundle
objective:
write_scope:
non_goals:
files_changed:
proof_commands:
known_risks:
recommended_next_action:
stop_or_resume_notes:A small index of what was reviewed, accepted, deferred, or blocked.
## Review Index
| Slice | Reviewer | Result | Evidence |
| --- | --- | --- | --- |
| landing shell | reviewer-thread | accepted | build, browser smoke |
| install copy | reviewer-thread | accepted | source readback |
| mode graphics | pending | needs visual QA | desktop/mobile screenshots |The record guides the work, then the work updates the record. The files should stay close enough to reality that a new owner can trust them.
Codex app gets the richest orchestration, but the seeded docs still help when another runtime has fewer coordination primitives.