spec

OwnFramework Loop - spec

This skill is a host adapter over the deterministic ofloop core.

Rules

• Never approve your own packet.
• Never write STATE.json, APPROVAL.json, REVIEW_VERDICT.json, event logs, or lock files directly.
• Never manufacture the TTY confirmation token.
• Never add push, merge, deploy, publish, send, payment, or unrelated remote authority.

New specification (normal flow)

1. Confirm the working directory is the target Git repository.
2. Resolve repository identity BEFORE creating the run:
   • inspect configured Git remotes;
   • decide the packet classification from actual current state, not intended future state;
   • local_only means no configured remote;
   • when a private GitHub review surface is part of the project, create/configure it, push the intended baseline, prove local/remote parity, and use github_private before ofloop spec new;
   • do not mint a local-only run and add a remote afterward.
3. Inspect only enough repository context to draft an accurate bounded packet.
4. Use ofloop spec new "" to create the run.
5. Draft WORK_PACKET.md using the repository schema and packet conventions. Declare portable capabilities for host/tool needs instead of embedding machine paths or manually reconstructing tool-specific network topology (for example toolchain.python, package.uv, browser.playwright.chromium). Use runner_profile only as a trusted profile NAME when the mission needs an operator-commissioned model/effort policy; packets never carry raw Claude flags. Always write runner_profile explicitly in newly authored current packets. Use default only when the operator intentionally accepts no Loop model pin: the commissioned runner environment may select the model (for example through ANTHROPIC_MODEL), otherwise the provider default applies. The commissioned Claude runner does not reread interactive user/project/local Claude settings (including ~/.claude/settings.json); a specific model belongs in a trusted named runner profile, while provider endpoint/auth belongs in the private commissioned service environment. Use network_read_allowlist only for packet-specific extra read hosts not already supplied by a capability contract. Never add a broad wildcard, scheme, port, path, publish endpoint, daemon socket, or unrelated host. Before enqueue, run ofloop capabilities probe to inspect the host and ofloop capabilities preflight <repo> <capability>... for the exact requested set. If a requested ordinary capability is unavailable, provision or commission it on the host or revise the packet before execution; do not widen HOME/PATH or fall back to unsandboxed execution. Privileged container.docker / local.http-service additionally require the operator-owned canary commissioning flow.
6. For PROGRAM packets with checkpoint-specific outcomes, keep the complete mission acceptance contract at top level and assign it deterministically with each checkpoint's acceptance_criterion_ids. If any checkpoint uses scoped AC ids, every checkpoint must declare a non-empty list and the union must cover every top-level AC id. Do not use not_applicable for future checkpoint criteria merely to satisfy coverage.
7. Validate the packet shape with the supported validator.
8. Return to the operator: