1.6 KiB
1.6 KiB
ADR-000: Scope and Non-Goals
Status
Accepted.
Context
as4-411 must have a locked scope so that "interact" is not interpreted as brokering, orchestration, or config generation. The system boundary and trust model depend on this.
Decision
In Scope
- as4-411 is a directory + discovery + routing directive generator.
- It stores participants, identifiers, endpoints, capabilities, credentials references, and policies.
- It resolves identifiers to routing directives (target protocol, address, profile, security refs, QoS). Gateways execute these directives; as4-411 does not transmit messages on their behalf.
Out of Scope (Unless Explicitly Added Later)
- Brokering / orchestration: Sending or relaying messages between parties is out of scope. If added in the future, it must be a separate component (e.g.
as4-411-broker) with a separate trust boundary so the directory's integrity and confidentiality are not contaminated. - Config generation for multiple gateway stacks: Generating full gateway configuration (e.g. PMode files, STP config) may be added as a separate tool or module; it is not part of the core directory/resolver.
Integration Default
- Gateways may consume as4-411 as an embedded library (core + resolver + storage) or as a sidecar/shared service (REST or gRPC). The default pattern is documented in the README and deployment docs; both are supported.
Consequences
- All feature work stays within directory, discovery, and directive generation.
- Brokering or message transmission, if ever required, is a distinct service with its own security and compliance story.