Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt

Use this file to discover all available pages before exploring further.

Feature IDs: GR-10, GR-UX-10
Feature Status: ✅ Complete
Last Updated: 2026-04-15
Owning Core: GR (Governance and Compliance)
Constitution Reference: Section 1.3 (cross-core integration through platform layers and contracts)

​
Overview

GR-10 and GR-UX-10 currently keep contract creation inside GR core boundaries and do not introduce new cross-core event contracts. Contract records are persisted in gr_contracts using the existing mutation flow.

​
Event Contract Scope

Status: ✅ Explicitly out of scope for GR-UX-10 v1. No new domain event types are introduced for wizard lifecycle actions or successful contract inserts beyond existing GR-10 behavior. Publisher: GR (Governance and Compliance), using gr_contracts as the source of truth. Wizard analytics boundary: gr_contract_wizard_* signals in the UX implementation are product analytics events only. They are not registered as cross-core event contracts until payloads are standardized to IDs-only and a channel (for example gr_events or PF-10) is agreed with subscribers.

​
Implementation Note

Use useContractMutation().createContract for contract creation. TanStack Query invalidation for contract list and detail queries is handled by the hook. If a future contract_created (or equivalent) domain event is needed for FW, notifications, or FA subscribers, add that contract under GR-10 in EVENT_CONTRACTS.md with a typed payload and documented subscribers.

​
References