Overview — IP and ownership structure
Mars® Spec › Overview › IP and ownership structure
← Canonical definitions · Section index
7. IP and ownership structure
| Component | Owner | Basis |
|---|---|---|
| 01-juno | Causum | Multi-order multi-perspective multi-variant formal domain model; order decomposition (domain aspects, per-order synthesis, seven-field relational metric records); perspective constitution (generative six-step pipeline, perspective tags, cross-perspective relationship records, per-perspective relational quantification); variant declaration (exact six-field record, variant consistency map with per-element and per-pair entries carrying seven required fields, variant verification with independence requirement, lossy-provenance flag propagation); order-typed DSL (identity/separate-artifact/typeclass embodiments, admissibility relation as declared registered artifact with amendment lifecycle, mechanical two-layer type enforcement, typed rejection diagnosis as registered output, higher-order orders as admissibility-relation extenders, order-typed soundness inheritance); formal specification five-component bundle (compiled predicates, well-formedness discharge record, adjudication record, scope-of-applicability certificate, soundness declaration); boundary-closure attestation with per-order/per-perspective/per-variant content hashes and certifying adjudication trust signal; model lifecycle and delta-attestation; completeness and gap referral; higher-order synthesis (unconstrained input selection, depth-n); governing selection and activation (governing collection, activation condition schema, dimension-level activation, governing-conflict gap type, conflict resolution procedure taxonomy, conflict-as-verdict-annotation) |
| 02a | Causum | Analysis battery (pre-IR, IR-level, post-IR); traversability (metric space, controlled embedding transformations, governing structural invariant, traversal witness); multi-perspective/multi-order/multi-source analysis; symbolic lift and order-typed representation; intermediate representations and multi-stage pipelines; reverse-composition; divergence signal with declared aggregation function; battery execution and verdict discipline (per-pass audit chain, mechanical tri-state status, anchor-inheritance annotation, PV-gate, AR-gate with full AUTHORITY_RECONCILE protocol: peer-finding message format, no-unverified-propagation invariant, divergence detection, ReconciliationEvent, verdict downgrade, four-outcome resolution enumeration, partition-recovery protocol, capability advertisement); gap analysis and typed gap referrals (locus taxonomy including governing-conflict); externally-observable properties (SA1–SA16, R1–R10, IR1–IR9, B1–B12, V1–V11, G3/G7–G11, T1–T6, F1–F9) |
| 02b | Causum | Conformance certificate (nine co-required structural invariants, nine-field canonical realization); specification registry; certificate composition and N-hop certificates (atomicity, recursive composition); delta-attestation lifecycle (delta-attestation object with seven properties, scope classification, cascade obligations, re-discharge module, cross-portfolio cascade); governance variations including federated joint-authority certification (AUTHORITY_RECONCILE cross-reference, federation hash computable only after AR-gate clearance); ON_CHAIN_ANCHOR pattern (verify-then-commit inversion: only CERTIFY verdict hashes reach the distributed ledger; chaincode-commitment field on PassRecord with bidirectional txid linkage; structural orthogonality to internal audit-chain tamper-evidence; multi-chain abstraction; DDIL edge-queuing with causal-order reconnection commitment) |
| 02c | Causum | Non-language-provenance anchor (seven structural invariants); downstream verification gate (five refusal conditions) with battery-method linkage; procedural-confidence derivation function with declared weight registration; scope-of-applicability certificates; N-hop composed scope certificates; NB1/NB2 enforcement constraints; actuation anchor (seven structural invariants); downstream actuation gate; NB3/NB4/NB5 enforcement constraints; named-authority standing registry; bidirectional boundary closure; interaction-protocol lift to order-typed form |
| 02d | Causum | Composed discrete program; model-as-map layered architecture; cross-model composition; subject-directed determinations |
| 02e | Causum | Pre-invocation signal registry; signal typing against order structure; witness classes and chain integration; pre-invocation signals and the divergence signal; signal-absence postures; AIGP pre-invocation governance specification; five architectural refusals (negative-space discipline) |
| 02f | Causum | Post-hoc forensic layer: evidence trail; inter-AI analyst orchestration; causal attribution; adaptive posture; temporal-chain forensics; reinforcement-action layer; post-hoc artifact attribution |
| 03-i | Causum | Semantic binding; data source characterization; Pymnemon and Impera client classes; connect/traverse/query admission; aspect-keyed query library; multi-locus gap report |
| 03-ii | Causum | Aspect-typed primitive extraction; co-indexed bidirectional store; bidirectional symbolic-embedding round-trip; controlled embedding-space transformations; map-governed chunking with subchunk expression; KB lifecycle; formal specification as KB variant; validity determination via adjudication record (third bundle component) |
| 03-iii | Causum | Evidence-gathering verification; governing specification as view over governing collection (§01 §12.1); grounded conformance verdict; recomputation witness (two required components); symmetric reinforcement (locus taxonomy including governing-conflict, distinct from specification-gap); perspective specifications; reinforcement loop discipline; gap governance state machine (Open/In-resolution/Resolved/Declared-permanent) governing governing-conflict gaps; terminal conformance certificate |
| 03-iv | Causum | Governed data generation; governed benchmark generation; model evaluation scenarios; benchmark consumer interface; benchmark lifecycle |
| 03-v | Causum | Governed-service discipline; governed-service externally-observable properties |
Mars® is the name for the system as a whole. The three layers — Juno, Jupiter, Minerva — are not independent products. The inventive novelty of each derives from its composition under the order-decomposition. Practicing any single layer in isolation, without the order-typed structure in the critical path of the mechanism, does not practice the governed architecture. The admissibility relation (01-juno §6), the soundness declaration (01-juno §7), the AUTHORITY_RECONCILE protocol (02a §3a.3), the delta-attestation lifecycle (02b), and the governing-conflict gap type (01-juno §12.4, 02a §7, 03-iii) are co-required structural elements of the architecture; omitting or substituting any of them produces a non-conforming variant regardless of resemblance in output.