Observable semantics are part of a system's design, not Bridge runtime state. Record them in ordinary, version-controlled design documentation next to the subsystem they describe.
Bridge does not define or validate a special observable-contract artifact. A design document does not prove that instrumentation or trace validation exists, and its presence does not satisfy an evidence obligation. Configure executable trace, runtime, or model-comparison commands in the project profile; Bridge evaluates their evidence receipts.
For each observable or event, state the details that a reader cannot safely infer from code alone:
Prefer precise prose, tables, and diagrams over a schema-shaped checklist. Link to implementation and executable evidence where useful.
Use profile and policy configuration to connect this documentation to Bridge's change and evidence loop:
docs-globs;file-glob-rules and concern-class to provide context matched by policy rules;This keeps semantic knowledge reviewable while leaving obligation inference and freshness to Bridge's profile, candidate state, and evidence receipts.
See the DPDK ring example for one possible document shape.
Can you improve this documentation?Edit on GitHub
cljdoc builds & hosts documentation for Clojure/Script libraries
| Ctrl+k | Jump to recent docs |
| ← | Move to previous article |
| → | Move to next article |
| Ctrl+/ | Jump to the search field |