Skip to content

SP-PATT-WARR-001 L0: normative pattern-warrant schemas + conformance#203

Closed
mdheller wants to merge 1 commit into
mainfrom
feat/sp-patt-warr-001-schemas
Closed

SP-PATT-WARR-001 L0: normative pattern-warrant schemas + conformance#203
mdheller wants to merge 1 commit into
mainfrom
feat/sp-patt-warr-001-schemas

Conversation

@mdheller

Copy link
Copy Markdown
Contributor

SP-PATT-WARR-001 — Layer 0 (normative foundation)

First of 8 layers implementing the Pattern-Warranted Agent Manifest Pipeline. Inverts the behavioral-analytics observe→count→threshold→spawn sequence: evidence informs which quorum is required and whether a manifest may be proposed; it never authorizes. Authority is granted only by signed attestations meeting Q(C).

What's here (spec-only, no runtime)

  • 8 JSON Schemas under schemas/EvidenceAtom, PatternAtom, ConsentAtom, AttestationAtom, WarrantEdge, CandidateManifest, WarrantLattice, AbstentionEvent. Conformed to the repo schemas.srcos.ai/v2 convention (id + type const + specVersion, additionalProperties:false); draft socioprophet.ai $ids normalized.
  • Canonical lattice (examples/warrant-lattice.default.json) — minW, quorum Q(C), decay half-lives 180/90/30/14d, hysteresis dwell 7d/2d, §2.2 concentration caps.
  • Spec doc (specs/pattern-warranted-manifest.md) — invariants, Grant predicate, $id mapping, OI-1..4 resolutions.
  • §9 conformance vectors (fixtures/pattern-warrant/conformance.json) T1–T7.
  • Executable validator — recomputes ceiling()/grant() over the lattice; mechanically enforces SP-PW-I1 (no score authorizes) and SP-PW-I2 (ZERO never NEG). Wired into make validate.

Verification

make validate-pattern-warrant-examples → 15/15 checks green (schema conformance + executable §9 vectors incl. I1 strip-attestations negative control and I2 const:ZERO).

Next layers (strict dependency order)

L1 hellgraph atoms → L2 scope-d scorer → L3 mellumwork (new) → L4 agent-registry gate → L5 policyfabric (new) → L6 agentplane binding → L7 evidence consumer.

🤖 Generated with Claude Code

…mance

Land the normative artifacts for the Pattern-Warranted Agent Manifest
Pipeline (SP-PATT-WARR-001). Evidence informs but never authorizes:
authority is granted only by signed attestations meeting Q(C).

- 8 JSON schemas (EvidenceAtom, PatternAtom, ConsentAtom, AttestationAtom,
  WarrantEdge, CandidateManifest, WarrantLattice, AbstentionEvent),
  conformed to the schemas.srcos.ai/v2 convention (id+type const+specVersion,
  additionalProperties:false). Draft $id URIs normalized off socioprophet.ai.
- Canonical default lattice: minW, quorum Q(C), decay half-lives
  (180/90/30/14d), hysteresis dwell (7d/2d), §2.2 concentration caps.
- Executable validator recomputes ceiling()/grant() over the lattice and
  runs the §9 conformance vectors, mechanically enforcing SP-PW-I1
  (no score authorizes) and SP-PW-I2 (ZERO is never NEG). Wired into
  `make validate`.

Refs: SP-PATT-WARR-001 §1-§9. First layer of the 8-layer build.
@mdheller

Copy link
Copy Markdown
Contributor Author

Superseded by architectural pivot. The pattern-warrant pipeline is now absorbed into Mellumwork as its agent-authority Episode profile, under a brand-neutral steward-owned namespace (schemas.socioprophet.io/mellumwork/) rather than the OS-tied srcos.ai namespace this PR used. Rationale: a schema $id bound to a product/OS brand rots when the brand is renamed — the same abandonment-death the system is built to resist. Concepts preserved: CandidateManifest → agent-authority Episode; W_p(t) → tier decay; ceiling/abstention (I1/I2) → authority block; attestation quorum → L3 Attestation. Closing rather than merging; no content lost.

@mdheller mdheller closed this Jul 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant