Commission and coordinate bounded work

A useful brief gives an executor enough purpose to make sound local choices and enough boundary to avoid inventing authority. It states the result and its use; accepted basis; relevant sources and scope; exact allowed writes; exclusions; required checks; expected return; parent; and return path. Small read-only work can use the retained launch message itself. Larger or governed work needs the structured record required by its method. Do not duplicate forms solely to make a small task look formal. Root entry · Runtime contract · App instructions

For software-bounded-implementation, the required brief names ScopePath, selected Workflow, PackageID, DeliverableIDs, Objective, AcceptedBasis, AllowedWriteTargets, EXCLUSIONS, AcceptanceCriteria, ExpectedReturn, PROFILE_PATH, and ApplyEdits: true. The profile identifies registered checks; the brief supplies the applicable execution authorization. If write authority is absent, the executor returns a proposal rather than applying changes. Bounded implementation brief

Before launch, preserve the supplied basis and actual method identity. Under governed delegation, sealing and the applicable human authorization are requirements; a nonempty approval-reference field does not establish that approval occurred. Cite an existing applicable owner act when it already authorizes the assignment. Do not manufacture a new permission ceremony or invent approval-token syntax. If a particular workflow reserves a fresh gate, prepare its concrete decision package before pausing at that gate. CONTRACT K-SEAL-1 · Chirality change conventions

Record actual parentage and mechanism. Distinguish a managed child session from a native descendant, a prepared brief from an executing child, and intended model allocation from observed model identity. Retain the actual supplied role, sources, selected methods/resources, revisions or hashes, relevant permissions, substitutions, and enforcement limits. A same-model independent review may still be useful, but must not be described as model diversity. D-GOV-35 · Runtime contract · Piping review rules

Give concurrent workers disjoint writes or explicit serialized ownership. Include generated artifacts, shared configuration, graphs, and evidence destinations. Separate files do not guarantee technical independence: two workers can implement incompatible assumptions about the same interface. Bind the shared contract and revision in both briefs and identify the owner of any change. A common test database, browser, native application, or port can also require serialized use even when source changes are independent. Runtime contract, coordination and evidence · App instructions

TASK reports findings to its parent. The parent assesses consequences and relays the relevant information to affected workers, with its standing intact: observation, hypothesis, proposal, or accepted decision. A changed file on disk does not prove that a running child received amended instructions. Supply a versioned brief amendment through the available mechanism and establish its receipt before relying on affected continuation. Preserve prior basis and history. Runtime contract · TASK

On return, examine artifacts and evidence against the brief. Check scope, changed paths, fulfilled criteria, missed interfaces, unresolved findings, and the contribution's fit with the receiving state. Distinguish usable partial work from completion. A manager who silently fills gaps in a child's report can obscure what the child actually did; retain the original return and record the parent's assessment and any authorized repair separately. WORKING_ITEMS · Runtime contract

Adjust delegation when evidence calls for it. Repeated repair attempts without new information need a changed diagnosis or narrower question. A queue of unexamined returns needs review and integration capacity before more production. When uncertain shared definitions dominate, concentrate that design work; when established interfaces permit independence, increase useful concurrency. These are implementation choices within the approved strategy, not reasons to invent standing staffing quotas. Piping instructions · Human manual §§4.3, 4.6, 5.4