PLATFORM MESH → FED8RA: PREPARED INTEGRATION HANDOFF
14 October 2026. Proposal; no deployment or external writes.

WHAT IS READY
- Static explorer with relative assets, explicit ?embed=1 mode and no runtime
  package/CDN dependency. It performs same-origin GETs for its public fixtures.
- Versioned event.schema.json, deterministic external event IDs and 30 fixtures.
- adapter.js validates the envelope and produces an EVIDENCE_CANDIDATE after
  explicit organization and case→collaboration mappings. It never authorizes,
  imports, accepts delivery, invoices, pays or sends to the rail.
- Separate source modes: synthetic_fixture, lab_observation, partner_source.
  New fixtures are UNSEALED. Historical summaries are not used to upgrade them.
- Exact business context: case_id, order_id, agreement_id, organization_id,
  service_id, resource_uid/resource_version; event and observation time.
- Existing four roles and 150 historical workload identities remain unchanged.

REUSE THE EXISTING FED8RA PATH
The read-only review used TRU-wallet-phase37/docs/FED8RA_INTEGRATION_HANDOFF.md,
including its 13 October update. It describes collaborations, company roles,
contribution criteria, evidence, reviews, accepted quantities, disputes and
clearing. This is a reference snapshot, not a claim about today's deployed state.

Proposed mapping (must be validated with the owning implementation):
  organization_id -> existing canonical company/member identity and source role
  case_id -> existing collaboration, using an explicit operator-supplied map
  order_id -> external order reference, not a new competing internal order table
  agreement_id -> existing accepted terms/version linkage
  event_id + source_adapter -> source deduplication identity
  usage.measured -> contribution/evidence candidate with unit and time interval
  instance.failed -> execution evidence and retry/cancellation context
  delivery.accepted -> claimed source action; host must authenticate authority
  review.requested -> request for review; never an automatic Chamber ruling
  content_sha256 -> payload integrity and conflict detection

No official fed8ra endpoint or database schema is invented here. The projection
is explicitly cotrugli.fed8ra-import-candidate.v1, not a supported fed8ra API.

WHAT STILL NEEDS HOST-SIDE WORK
1. Match every source identity to the current member, company edge and permission
   scope. The authenticated company action journal must decide who may submit.
2. Create/reuse the target collaboration and accepted terms. Reject unknown
   mapping, unknown versions and mismatched agreement/resource references.
3. Import through the existing business action/evidence interface. Persist a
   durable inbox unique on source_adapter + event_id: identical hash = retry;
   different hash = conflict requiring review. Record the durable result before
   acknowledging. The provided adapter is pure and has no durable inbox.
4. Use the existing outbox, owner edge and n8client for evidence commitments;
   preserve exact request bytes and independently verify N8CF1/chain before
   showing FINAL. No JSON/ShareBundle on the binary rail. Use the existing
   scoped business-sharing channel for business objects.
5. Read acceptance, dispute, clearing and payment from their actual host
   authorities. Source claims must never advance these states on their own.
6. Feed status back by case/order/record correlation. Keep source collection,
   booking, finality, execution, business acceptance and payment distinct.
7. Validate resource versions, accepted claims, audit.actor provenance and
   authoritative meter semantics against the target KCP installation. The
   recorded run used kcp 0.31.0 and Platform Mesh chart 0.3.0.

EMBEDDING
Serve site/demo/8ra/market-mesh/ under a host-controlled subpath and load
?embed=1. Relative asset URLs support that placement. Embed mode hides outer
navigation/hero/footer; it exposes no postMessage channel and receives no
credentials. The supplied embed-example.html tests a trusted same-origin iframe. For an
isolated, separately hosted module use sandbox="allow-scripts allow-same-origin
allow-downloads" and verify host policy. Omitting allow-same-origin makes the
frame an opaque origin and prevents its normal same-origin JSON fetches. Never
combine script/same-origin sandbox permissions with untrusted same-origin
content. Prefer a separately hosted origin for untrusted content. Set the host's
frame-src/CSP and the module server's frame-ancestors policy intentionally.
For a native view, use scenarios.json and adapter.js instead of scraping DOM.

ACCEPTANCE TESTS BEFORE CONNECTION
- Authenticated party A cannot submit as party B or target another collaboration.
- Unknown organization/case, wrong source role and unknown schema are refused.
- Exact replay before/after restart creates one import; changed content under the
  same ID raises a conflict. Crash before acknowledgement is recoverable.
- Technical Ready or a valid hash does not accept delivery or invoice/payment.
- A source assertion of FINAL is ignored until the host's verifier confirms it.
- Synthetic fixtures cannot become production evidence; use a disposable lab.
- Cleanup covers Chat UI, both bindings, token revocation/deletion and LLM.
- No new rail transport, producer, identity roster or business authority.

FABLE BOUNDARY
No running fed8ra services, shared checkout, registry, wallets, Chamber or rail
configuration was changed. No message was sent to Fable. The adapter and this
handoff can be reviewed after his integration work without introducing a
parallel state store or a second rail sender.

FOLLOW-UP RECORD — 14 October 2026
Status: PROPOSED. See MARKET-MESH-INTEGRATION-PROPOSED-20261014.txt.
Recorded before host import code, following neoos-stack #685.