§03-v Minerva — Governed Services — What this section covers
Mars® Spec › §03-v Minerva — Governed Services › What this section covers
Section index · Governed-service discipline →
Mars® Protocol — §03-v: Governed Services
Version 1.0-draft
1. What this section covers
This section specifies the governed-service discipline: the structural requirements that apply when the governed pipeline — modeling, analysis, and artifact creation — is exposed as a callable, registered, versioned, audit-emitting service. A governed service is not merely a generation pipeline; it is a generation pipeline whose every operation is itself a governed act, registered in the specification registry, version-stamped, and audit-emitting, with each output artifact order-typed and bound to its governing assets by a recomputation witness.
What this section does not cover. This section does not re-specify the generation operations themselves — governed data generation (§03-iv §2), governed benchmark generation (§03-iv §3), KB creation (§03-ii), or semantic binding (§03-i). Those sections govern what is produced; this section governs the service discipline under which those operations are exposed and composed. References to those sections are cross-references, not re-specifications.
Dependencies:
- §01 (modeling) — provides the domain model (one or more, composable and independently operable; see §01 §1) governing all generation operations; where multiple domain models are active, each service operation records the domain model version(s) that governed its governing assets in its audit record
- §02b (delta-attestation lifecycle, specification registry, governed-generation artifacts) — governs versioning and registration of generated artifacts and service records
- §03-i — provides the data source metadata machinery (characterization, semantic binding, aspect-keyed query library) and the data source bootstrapping path; the metadata built here is the data-layer input to attribution (§03-iii §2.12)
- §03-ii — provides the KB metadata machinery (aspect-typed extraction, co-indexed bidirectional store, formal specification definition) and the KB/formal-spec bootstrapping path; KB metadata is the governance-layer input to attribution (§03-iii §2.12)
- §03-iii — provides the evidence-gathering and attribution machinery consumed by all service operations; §03-iii §2.12 (attribution) governs how service outputs — including summarization outputs and analytical findings — are bound back to the artifact(s) that govern or support them; §03-iii §2.2 governs the governing specification as an active collection of formal specifications
- §03-iv — provides the governed data generation, benchmark generation, and model evaluation operations composed under the governed-service discipline