namespace-is-colon-convention-with-auto-wiring
IN derived (depth 1)
The namespace system is a colon-based convention with automatic infrastructure wiring: colon presence prevents double-prefixing, the `agent:id` format provides scoping, and node creation auto-wires a `{ns}:active` premise as an antecedent.
Summary
When an agent uses namespaced beliefs, three things work together as a convention: colons in node IDs signal that a reference is already namespaced so the system won't accidentally double-prefix it, the agent:id format naturally scopes beliefs to their owner, and creating any node in a namespace automatically hooks it up to a single active premise that acts as a kill switch for that entire namespace.
Justifications
SL — Three namespace beliefs define a complete convention: format, idempotency guard, and automatic kill-switch wiring
Antecedents (all must be IN):
- namespace-prefix-is-colon-separated — Agent namespacing uses the format `agent_name:belief_id`; `_resolve_namespace()` skips prefixing any ID that already contains a colon, preventing double-prefixing of cross-namespace references
- colon-means-already-namespaced — `_resolve_namespace` treats a colon in a node ID as "already namespaced" and never double-prefixes; this is the convention for cross-namespace references.
- namespace-active-premise-invariant — When `namespace` is set, `add_node` auto-creates a `{namespace}:active` premise node and wires it as an antecedent into every namespaced justification; retracting that single premise cascades OUT every belief from that namespace.
Dependents
These beliefs depend on this one:
- all-identification-is-deterministic-and-collision-free — All system-generated identifiers — dialectical artifact auto-IDs, unconditionally-recorded nogood records, and colon-based agent namespace prefixes — follow deterministic patterns that prevent collisions across all three identifier spaces: dialectical, contradiction, and multi-agent.
- import-provides-complete-reconciliation — The import subsystem provides complete reconciliation coverage: heterogeneous truth states are handled correctly on initial load, dual modes support additive import and remote-wins sync for different operational needs, and the colon-based namespace convention with auto-wiring prevents ID collisions across agents.