Skip to content

docs: record the intent architecture (venue adapters, egress guard) #131

Description

@mfw78

Problem. The CoW integration is the engine's only domain-specific code (shepherd:cow/cow-api + the cow_orderbook backend), and it is compiled in. The next domains are a Swarm postage purchase and an off-chain marketplace, venues must be user-installable without app-store deployments on mobile/super-app targets, and the wallet embedding needs decoded/simulated signing payloads fed to installable threat-analysis components. There is no recorded design covering these.

Proposed. Record the agreed target architecture as a design doc plus two ADRs: venues become dynamically installed adapter components (CoW is the first, bundled not compiled-in) over a typed nexum:value/nexum:intent ontology with host-derived headers, and one egress guard pipeline (facts -> analysers -> binding policy with override) covering intent submissions, EIP-712 signing, and transaction signing, with simulate as a pluggable host primitive.

Scope. Documentation only; implementation epics follow separately along the sequencing section of the design doc.

Metadata

Metadata

Assignees

No one assigned

    Labels

    docsDocumentation is wrong or missing.needs-designRequires thinking. No one has bandwidth.

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions