The Federation Prime Contractor

Define the fictional intake pilot, required artifacts, delivery sequence, and prime-only team scope. Explicitly separate discovery references from contracts, federation activation, and cross-world registration.

Inputs: starter/case/engagement.json, starter/interfaces/pilot.json, starter/data/deliverables.csv, starter/data/dependencies.csv, starter/data/acceptance-matrix.csv, starter/governance/public-artifact-boundary.json

Outputs: deliverables/prime-scope.json

Depends on: No prerequisites

• Includes 60 synthetic attendees, a 120-minute retention ceiling, and the anonymous ticket field allowlist.
• States that all five prime teams share only demo-federation-prime-contractor and no candidate workspace is registered there.
• Contains no approved external effect or claim that a partner has agreed to work.

Turn the applied-invention-lab brief into an owner-reviewable discovery request covering the local prototype interface and limitations. It is not a sent request or contract.

Inputs: starter/briefs/applied-invention-lab.json, starter/interfaces/pilot.json, deliverables/prime-scope.json

Outputs: deliverables/lab-discovery-request.json

Depends on: freeze-prime-engagement

• Names the candidate slug and prototype-spec deliverable, interface fields, and exact acceptance criteria.
• Labels the relationship discovery-only and the request unsent/unapproved; offers no remote authority.

Prepare the enterprise-transformation-firm discovery request, explicitly depending on the reviewed prototype interface rather than a registered foreign workspace or assumed partner result.

Inputs: starter/briefs/enterprise-transformation-firm.json, starter/interfaces/pilot.json, deliverables/prime-scope.json, deliverables/lab-discovery-request.json

Outputs: deliverables/process-discovery-request.json

Depends on: draft-lab-discovery-brief

• Includes greeter, queue-steward, and closeout-reviewer roles, a bounded stop condition, and retention no longer than 120 minutes.
• States that only a separately owner-approved public artifact could satisfy the cross-organization handoff.

Prepare the product-launch-company discovery request for a closed synthetic rehearsal kit. Carry the upstream interface and operating-model dependencies and prohibit public-launch claims.

Inputs: starter/briefs/product-launch-company.json, starter/interfaces/pilot.json, deliverables/process-discovery-request.json, deliverables/lab-discovery-request.json

Outputs: deliverables/launch-discovery-request.json

Depends on: draft-process-discovery-brief

• Requires at least four concrete operator steps, the exact interface version, SYNTHETIC disclosure, owner review, and no public launch.
• Remains an unapproved discovery packet, not advertising authorization or partner activation.

Run the authored utility tests and inspect the explicit deliverable/dependency/matrix inputs. Validate only local inert JSON; do not import code, contact a partner, or add a workspace pointer.

Inputs: starter/interfaces/pilot.json, starter/data/deliverables.csv, starter/data/dependencies.csv, starter/data/acceptance-matrix.csv, starter/fixtures/submissions.json, starter/fixtures/rework-submissions.json, starter/tools/acceptance.py, starter/tests/test_acceptance.py, deliverables/prime-scope.json

Outputs: deliverables/interface-validation.json

Depends on: freeze-prime-engagement

• Rejects unknown rules, duplicate artifacts, cycles, unknown candidates, and unexpected artifact fields.
• Confirms an acyclic dependency chain from prototype to operating model and pilot kit to the prime's derived report.
• Describes offline behavior flags as content declarations, not dynamic proof that a partner application works.

Run the baseline fixture through the content matrix. Record exact failed criteria, source locations, downstream blockage, and the fact that these are authored examples rather than real submissions.

Inputs: starter/fixtures/submissions.json, starter/data/acceptance-matrix.csv, starter/data/dependencies.csv, starter/tools/acceptance.py, deliverables/interface-validation.json

Outputs: deliverables/rejection-rehearsal.json

Depends on: verify-local-interface

• Prototype content passes, operating-model retention 1440 fails the 1–120 bound, pilot-kit interface version 0 fails version 1, and integration-report is blocked.
• Captures the expected nonzero baseline CLI exit code and does not call a failed baseline a tool malfunction.
• Reports delivery_authorized false and no cross-world effects.

Review the rejection report and original change/risk rows. Specify minimal corrections, affected dependents, and renewed review gates; do not silently weaken the acceptance matrix.

Inputs: starter/ops/change-requests.csv, starter/ops/risk-register.csv, starter/interfaces/pilot.json, deliverables/rejection-rehearsal.json

Outputs: deliverables/reference-rework-plan.json

Depends on: rehearse-explicit-rejection

• Proposes retention 120 and interface version 1, retaining both original failures as evidence.
• Identifies downstream pilot-kit/integration checks that must rerun.
• Does not approve the separate request to increase attendance to 90 or alter owner authority.

Use the included corrected fixture as a worked example, verify it against the bounded rework plan, and produce a proposed inert submission set. No actual partner artifact is fetched or exchanged.

Inputs: starter/fixtures/rework-submissions.json, starter/interfaces/pilot.json, starter/data/deliverables.csv, starter/data/dependencies.csv, deliverables/reference-rework-plan.json

Outputs: deliverables/proposed-reference-submissions.json

Depends on: bound-reference-rework

• Contains exactly the three declared reference artifacts with SYNTHETIC classification, candidate slugs, public-reference-fixture visibility, and no exchange approval.
• Carries no unknown payload fields, private content, executable partner code, remote locator, or workspace registration.

Apply the same eighteen criteria to the proposed reference set and record derived dependency acceptance. Keep content validity separate from actual delivery, performance testing, and owner approval.

Inputs: starter/data/acceptance-matrix.csv, starter/tools/acceptance.py, starter/tests/test_acceptance.py, deliverables/proposed-reference-submissions.json, deliverables/rejection-rehearsal.json

Outputs: deliverables/content-acceptance-rehearsal.json

Depends on: assemble-reference-rework

• All three corrected local fixtures and derived integration report satisfy content checks without changing the matrix.
• The report still says delivery_authorized false, real_partner_submissions false, and no external effects.
• Lists live usability, independent application verification, owner exchange approval, and commercial acceptance as unperformed.

Compare every discovery packet and acceptance result to the boundary policy. Record missing approvals, risk owners, and why no passing fixture can activate a federation or authorize remote work.

Inputs: starter/governance/public-artifact-boundary.json, starter/ops/risk-register.csv, deliverables/lab-discovery-request.json, deliverables/process-discovery-request.json, deliverables/launch-discovery-request.json, deliverables/content-acceptance-rehearsal.json

Outputs: deliverables/exchange-boundary-review.md

Depends on: draft-launch-discovery-brief, rehearse-content-acceptance

• States that independent organizations retain separate worlds and only owner-approved public artifacts may cross.
• Contains no foreign workspace registration, approved contract, membership, signing operation, federation activation, or delegated remote authority.
• Identifies real outreach and artifact exchange as future separately approved work, not performed effects.

Join scope, candidate packets, rejection/rework evidence, and the boundary review into a proposed next-step decision. Distinguish a useful local rehearsal from an actual contracted delivery.

Inputs: deliverables/prime-scope.json, deliverables/rejection-rehearsal.json, deliverables/content-acceptance-rehearsal.json, deliverables/exchange-boundary-review.md, starter/case/engagement.json

Outputs: deliverables/prime-owner-handoff.json

Depends on: review-public-exchange-boundary

• Explains the demonstrated rejection/rework chain and the unresolved real delivery/performance questions.
• Makes no activation, registration, contract, approved exchange, or real customer acceptance claim.
• Any next external action is a bounded proposal requiring explicit owner approval.