# Super Ontology Candidate Contract

The Super Ontology contract is a public-safe seed for adaptive knowledge
governance. It is not a claim that one ontology can perfectly cover every
future situation.

## Local Operator Mode

Public exports stay value-free and candidate-only. Local projects may use an
operator-managed promotion mode where the "gate" is not a generic security stop
sign.

In local operator mode, promotion checks mean:

- which project root owns this knowledge;
- which source folder or file produced it;
- who owns the decision;
- which evidence rows support it;
- which rollback or replay path can undo it.

Security, privacy, and confidentiality labels are routing metadata in this
mode. They organize context, folder placement, owner, audience, and retention;
they do not block local work by themselves when the operator has named the
structure above. Public releases still keep secret values out and keep broad
claims candidate-only until evidence exists.

## Files

Generated or packaged repos may include:

```text
.agentlas/
  super-ontology-contract.json
  super-ontology-open-world-coverage.json
  super-ontology-consensus-coordination.json
  super-ontology-task-coverage.json
  super-ontology-contextual-flow.json
  super-ontology-causal-impact.json
  super-ontology-assurance-case.json
  super-ontology-knowledge-homeostasis.json
  super-ontology-adversarial-provenance.json
  super-ontology-epistemic-calibration.json
  super-ontology-semantic-alignment.json
  super-ontology-resilience-control.json
  super-ontology-invariant-verification.json
  super-ontology-observability-telemetry.json
  super-ontology-objective-proxy-validity.json
  super-ontology-stakeholder-preference-governance.json
  super-ontology-normative-authority-drift.json
  super-ontology-side-effect-containment.json
  super-ontology-source-lineage-version.json
  super-ontology-entity-identity-resolution.json
  super-ontology-temporal-state-transition.json
  super-ontology-capability-delegation-authority.json
  super-ontology-privacy-confidentiality-boundary.json
  super-ontology-strategic-incentive-compatibility.json
  super-ontology-reflexive-feedback-stability.json
  super-ontology-replays.jsonl
  super-ontology-evidence.jsonl
  super-ontology-memory-bridge.jsonl
```

`super-ontology-contract.json`

- Describes the allowed ontology pipeline: source intake, evidence packets,
  belief ledger, knowledge capsules, affordance binding, open-world coverage,
  consensus coordination,
  task coverage,
  promotion readiness, replay drills, and rollback.
- Must set `runtimeGraphWriteEnabled` to `false` on export.
- Must set `zeroErrorClaim` to `false`.
- Must include `operatorManagedPromotion` metadata so local promotion can be
  decided by project/folder/owner/evidence/rollback structure instead of a
  generic security blocker.
- Must stay candidate-only for public export until shadow/canary replay,
  rollback, and sync review approve a later public phase.

`super-ontology-replays.jsonl`

- Append-only shadow, canary, rollback, and sync-review replay evidence.
- Empty on export.
- Runtime agents may append records later only after the local Memory Curator,
  PM Soul, or architecture sync owner approves the evidence boundary.

`super-ontology-evidence.jsonl`

- Append-only promotion evidence rows.
- Empty on export.
- Evidence must identify the proof key, target surface, status, and summary
  without storing private logs, local paths, credentials, or raw source content.

`super-ontology-memory-bridge.jsonl`

- Append-only Memory Curator bridge candidates.
- Empty on export; the public core repo may carry a public-safe seed row for
  schema visibility.
- Rows must keep `durable_write_enabled=false` until Memory Curator, Policy
  Gate, PM Soul, or architecture sync review accepts the ticket.
- Rows must not store raw prompts, secret values, private paths, full
  transcripts, or direct durable memory writes.

`super-ontology-open-world-coverage.json`

- Public-safe open-world coverage seed.
- Requires new world, task signal, modality, fault model, authority state, and
  write-surface combinations to stay candidate-only until fixture pressure,
  shadow replay, owner review, and sync review lower or approve authority.
- Keeps `runtimePromotionAllowed=false` on export.
- Blocks proposal/deck examples from being treated as proof that every future
  task is covered.

`super-ontology-consensus-coordination.json`

- Public-safe consensus coordination seed.
- Requires agent agreement, majority vote, debate, model-judge approval,
  distributed replica merge, and cross-runtime sync to remain candidate signals
  until independent evidence, veto roles, owner/policy review, sync review,
  invariants, and rollback are present.
- Keeps `runtimePromotionAllowed=false` on export.
- Blocks agent agreement, simple majority, debate stability, model-judge
  confidence, last-writer-wins route sync, and distributed replica merge from
  becoming write authority.

`super-ontology-task-coverage.json`

- Public-safe task-family coverage seed.
- Requires requests to be classified as read, draft, transform, analyze, plan,
  coordinate, execute, repair, personalize, regulated, multimodal, physical,
  software, finance/compliance, or education/coaching work before action.
- Keeps `runtimePromotionAllowed=false` on export.
- Blocks write, publish, execute, physical, and training tasks unless evidence
  mode, authority, review, and rollback are explicit.

`super-ontology-contextual-flow.json`

- Public-safe contextual-flow seed.
- Requires information flows to name source context, target context, sender,
  recipient, subject, attribute, transmission principle, purpose, authority,
  sensitivity, retention, controls, and audit references.
- Keeps `runtimePromotionAllowed=false` on export.
- Blocks same-user cross-context joins, tool responses treated as need-to-know,
  raw prompt or transcript memory writes, public output after private handoff,
  customer-data publication without consent, regulated training without delete
  path, and agent-internal traces in user output.

`super-ontology-causal-impact.json`

- Public-safe causal-impact seed.
- Requires state-changing work to name causal claim type, intervention target,
  expected outcomes, adverse outcomes, counterfactual checks, observability,
  reversibility, blast radius, blocked write surfaces, and rollback.
- Keeps `runtimePromotionAllowed=false` on export.
- Blocks correlation-as-causation, relation-as-permission, autonomous physical
  control, training without consent/delete path, and multi-agent writes without
  ordered handoff.

`super-ontology-assurance-case.json`

- Public-safe claim/evidence seed.
- Requires broad claims about coverage, memory safety, action safety,
  promotion readiness, red-team follow-up, or sync integrity to name required
  evidence, observed evidence, validators, residual risk, blocked shortcuts,
  and rollback.
- Keeps `runtimePromotionAllowed=false` on export.
- Treats literal perfection or zero-error language as a rejected overclaim, not
  a release state.

`super-ontology-knowledge-homeostasis.json`

- Public-safe knowledge-health seed.
- Requires stale, contradictory, unsupported, drifting, parser-failed,
  privacy-incident, missing-evidence, user-corrected, or runtime-desynced
  knowledge to name signal, measurement window, error budget, affected surface,
  control decision, escalation, evidence, Memory Curator policy, public export
  policy, and rollback.
- Keeps `runtimePromotionAllowed=false` on export.
- Blocks overrun budgets from continuing silently, critical cases from runtime
  writes, privacy incidents from public export, AppBridge routes from becoming
  source-write authority, and stale claims from becoming current truth.

`super-ontology-adversarial-provenance.json`

- Public-safe hostile-source provenance seed.
- Requires arbitrary uploads, web pages, emails, chats, tool responses,
  connector results, recalled memories, public repos, media assets, AppBridge
  routes, generated artifacts, and datasets to name claimed authority,
  provenance evidence, integrity checks, instruction policy, retrieval policy,
  memory policy, tool policy, promotion decision, forbidden shortcuts, and
  rollback.
- Keeps `runtimePromotionAllowed=false` on export.
- Blocks prompt injection from becoming instruction, poisoned sources from
  becoming memory, forged provenance from becoming trusted source, tool-output
  tampering from becoming action, route output from becoming source-write
  authority, and stale trusted-source replay from becoming current truth.

`super-ontology-epistemic-calibration.json`

- Public-safe uncertainty and abstention seed.
- Requires arbitrary future work to name context type, claim type, uncertainty
  source, epistemic state, calibration signal, confidence band, risk tier,
  allowed output, required controls, blocked shortcuts, evidence refs, research
  basis, memory policy, tool policy, public export policy, and rollback.
- Keeps `runtimePromotionAllowed=false` on export.
- Blocks missing evidence as complete answer, conflicting sources as current
  truth, low retrieval relevance as confident answer, noisy OCR as ontology
  class, model disagreement as consensus, inconclusive tool output as action,
  uncalibrated route sync, and wide judge intervals in regulated answers.

`super-ontology-semantic-alignment.json`

- Public-safe semantic alignment seed.
- Requires proposed glossary, schema, ontology, relation, hierarchy,
  entity-resolution, source-system merge, memory-merge, release-sync, or no-match
  decisions to name relation type, scope, ambiguity, semantic evidence,
  structural evidence, lexical evidence, negative evidence, validation checks,
  owner controls, blocked shortcuts, change policy, and rollback.
- Keeps `runtimePromotionAllowed=false` on export.
- Blocks same label as same meaning, embedding similarity as exact match,
  close-match as transitive truth, generated label as ontology class, OCR label
  as property alignment, AppBridge route as source ontology edit,
  same-individual without stable identifier, unit label without compatibility,
  source conflict as memory merge, and no-match promoted to weak match.

`super-ontology-resilience-control.json`

- Public-safe degraded-operation and self-adaptive control seed.
- Requires degraded operation to name control-loop phase, degradation signal,
  hazard type, operating mode, control decision, trigger threshold, observed
  evidence, feedback channels, controls, blocked shortcuts, Memory Curator
  policy, sync policy, and rollback.
- Keeps `runtimePromotionAllowed=false` on export.
- Blocks validator disagreement as graph write, retrieval drift as current
  answer, semantic regression as memory merge, provenance gap as tool authority,
  Memory Curator backlog as direct memory write, tool error spike as unbounded
  retry, unknown task as normal execution, context-flow violation as public
  export, sync drift as release surface, degraded parser as ontology class,
  rollback failure as runtime promotion, and AppBridge route as emergency-stop
  bypass.

`super-ontology-invariant-verification.json`

- Public-safe runtime-verification and temporal-invariant seed.
- Requires event streams such as source intake, evidence packets, belief
  updates, semantic alignment, resilience mode, memory tickets, graph writes,
  tool calls, public exports, route sync, release seeds, rollback, and
  emergency stop to be checked by explicit monitors before runtime writes.
- Keeps `runtimePromotionAllowed=false` on export.
- Blocks memory writes without curator-ticket invariants, graph writes without
  evidence invariants, tool actions without authority invariants, public export
  without contextual-flow invariants, route sync without source-contract
  invariants, rollback without observed feedback, emergency-stop bypass,
  unordered multi-agent writes, and non-idempotent replay mutation.

`super-ontology-observability-telemetry.json`

- Public-safe trace, span, correlation, audit, redaction, retention, snapshot,
  rollback, and alert seed.
- Requires source intake, evidence packets, belief updates, graph writes, memory
  tickets, tool actions, public exports, route sync, release seeds, repair
  events, rollback, and emergency stops to be reconstructable before runtime
  writes.
- Keeps `runtimePromotionAllowed=false` on export.
- Blocks writes without trace ids, memory tickets without span lineage, tool
  actions without audit receipts, public exports with stale metrics, route sync
  without correlation ids, release seeds when audit sinks are down, telemetry
  without redaction policy, green metrics without sample size, suppressed
  degraded-mode alerts, unrecorded shadow replays, repair without before/after
  snapshots, rollback without observed event, and unobservable runtime writes.

`super-ontology-objective-proxy-validity.json`

- Public-safe objective/proxy validity seed.
- Requires metric-driven work to name the real construct, proxy metric,
  stakeholder map, countermetric, validity evidence, gaming probe, and rollback
  before graph, memory, tool, route, release, or public writes can treat metric
  movement as success.
- Keeps `runtimePromotionAllowed=false` on export.
- Blocks approval rate, open rate, benchmark score, test pass rate, ontology
  edge count, self-judge score, short-term profit, green dashboards, and reward
  deltas from becoming authority without construct validity and anti-gaming
  evidence.

`super-ontology-stakeholder-preference-governance.json`

- Public-safe stakeholder preference governance seed.
- Requires preference-driven work to name stakeholder roles, preference
  sources, authority scope, affected parties, conflict type, aggregation rule,
  dissent capture, appeal path, review owner, consent or rights vetoes, and
  rollback before graph, memory, personalization, tool, route, release, public,
  training, customer-message, financial, hiring, health, physical, or
  runtime-policy writes can treat a preference as legitimate authority.
- Keeps `runtimePromotionAllowed=false` on export.
- Blocks owner preference, majority vote, behavior signals, role power, old
  preference records, hidden affected parties, missing dissent, and missing
  appeal paths from becoming write authority.

`super-ontology-normative-authority-drift.json`

- Public-safe normative authority drift seed.
- Requires policy-like, law-like, contract-like, license-like, consent-like,
  retention-like, emergency-exception, or professional-guideline sources to
  name primary source, version, effective date, jurisdiction scope, authority
  owner, precedence rule, exception owner and expiry where relevant, review
  owner, audit trail, and rollback before graph, memory, tool, route, release,
  public, training, customer-message, financial, hiring, health, physical,
  legal/compliance, or runtime-policy writes can treat a rule as current
  authority.
- Keeps `runtimePromotionAllowed=false` on export.
- Blocks stale policy, wrong jurisdiction, draft policy, superseded contract,
  expired consent, local custom, translation mismatch, summary-only regulation,
  license conflict, cross-border transfer gaps, emergency exceptions without
  expiry, and legal/compliance claims without review from becoming write
  authority.

`super-ontology-side-effect-containment.json`

- Public-safe side-effect containment seed.
- Requires side-effecting work to name the side-effect class, action surface,
  reversibility state, transaction boundary, idempotency state, blast radius,
  external commit state, containment evidence, approval, transaction log,
  compensation, cancellation, receipt, audit trace, rollback, and post-action
  verification before filesystem, external-send, payment, customer-record,
  public-release, cloud-admin, database, durable-memory, training, physical,
  route-sync, scheduled-job, or legal/compliance actions can execute.
- Keeps `runtimePromotionAllowed=false` on export.
- Blocks read permission as write permission, preview as send, dry-run as
  committed, non-idempotent retry, irreversible action without approval,
  deletion without recovery, payment without idempotency, release without
  rollback, partial failure without saga state, physical action without safety
  interlock, scheduled action without cancellation, and hosted tools without a
  local side-effect wrapper.

`super-ontology-source-lineage-version.json`

- Public-safe source lineage and version seed.
- Requires document-like artifacts to name source URI, checksum or content
  hash, version/revision, capture time, derivation chain, parent refs, primary
  source, authority owner, transformation log, parser version, chunk span,
  audit trace, and rollback where needed.
- Keeps `runtimePromotionAllowed=false` on export.
- Blocks filename-as-version, final-folder-as-current-source, PDF export as
  primary source, summary as primary source, OCR text without span, spreadsheet
  tab without workbook revision, stale connector cache as current record,
  chunk without source span, embedding hit without artifact version, Memory
  fact without lineage, public export without lineage, training example without
  dataset version, graph edge without derivation chain, superseded source to
  runtime write, and unresolved lineage cycles.

`super-ontology-entity-identity-resolution.json`

- Public-safe entity identity resolution seed.
- Requires names, aliases, email domains, phone numbers, CRM ids, employee ids,
  tax ids, spreadsheet rows, extracted mentions, external URIs, embedding
  clusters, redacted identifiers, merged records, and LLM-generated canonical
  labels to name canonical id, source-system namespace, entity type, source
  span, disambiguating attributes, negative evidence, temporal validity,
  tenant/context boundary, privacy basis, owner review, merge/split policy,
  tombstone, audit trace, and rollback where needed.
- Keeps `runtimePromotionAllowed=false` on export.
- Blocks name-as-identity, email-domain-as-company, fuzzy-match-as-merge,
  embedding-cluster-as-identity, LLM canonical name as id, cross-tenant CRM id
  merge, recycled employee id as same person, stale alias as current entity,
  redacted name as public identity, merged account without split policy, split
  entity without tombstone, external URI without context, relationship edge
  without identity evidence, and memory note as identity authority.

`super-ontology-temporal-state-transition.json`

- Public-safe temporal state transition seed.
- Requires current snapshots, local timestamps, spreadsheet row order,
  document revisions, webhooks, connector deltas, calendar holds, scheduled
  jobs, audit logs, migration batches, materialized views, LLM summaries,
  memory notes, and graph edges to name valid time, transaction time, event id,
  event sequence, source span, pre-state, post-state, state-machine rule,
  transition guard, idempotency, replay log, projection version, scheduler
  receipt, audit trace, and rollback where needed.
- Keeps `runtimePromotionAllowed=false` on export.
- Blocks current snapshot as truth, missing valid time, missing transaction
  time, local timestamp as global order, spreadsheet order as event order, LLM
  summary as event log, late event ignored, retroactive correction without
  transaction history, future-effective as current, expired state as active,
  deleted state without tombstone, non-idempotent replay, materialized view as
  source of truth, projection without version, recurring event without rule,
  timezone-free deadline, stale cache as current, state transition without
  precondition, partial failure as success, scheduled job without receipt,
  memory fact without validity interval, and graph edge without temporal
  bounds.

`super-ontology-capability-delegation-authority.json`

- Public-safe capability delegation authority seed.
- Requires roles, groups, OAuth scopes, API keys, service accounts, session
  cookies, tool schemas, cached policy decisions, broad approvals, delegation
  tokens, and child-agent authority to name actor, principal, task, operation,
  resource, scope, purpose, delegation chain, caveats, policy decision,
  revocation check, audit, rollback, and post-action verification before
  authority-bearing use.
- Keeps `runtimePromotionAllowed=false` on export.
- Blocks role-as-capability, OAuth scope as task permission, API key as actor,
  read access as write authority, unbounded parent-agent delegation, missing
  delegation chain, purpose mismatch, capability without caveats, stale token
  as current authority, cross-context capability reuse, tool-choice privilege
  escalation, child agent exceeding parent authority, reused human consent,
  permission prompt as policy, tool schema as authorization, cached auth
  decision without fresh context, break-glass without expiry, admin role as all
  actions, shared service account as identity, task goal as permission, and
  hidden tool calls without policy decisions.

`super-ontology-privacy-confidentiality-boundary.json`

- Public-safe privacy/confidentiality boundary seed.
- Requires PII, secrets, HR notes, legal privilege, personal diary context,
  customer decks, connector caches, screenshots, embeddings, inferred
  sensitive attributes, and company-confidential material to name
  classification, subject category, owner/controller, purpose, audience,
  legal or confidentiality basis, minimization, redaction, retention,
  transfer, public/training flags, access decision, audit, breach owner, and
  rollback before authority-bearing use.
- Keeps `runtimePromotionAllowed=false` on export.
- Blocks PII as normal fact, secrets as graph labels, customer decks as public
  context, missing consent/legal basis, private material as training data,
  public export without redaction, retention-expired memory, ignored deletion
  requests, cross-tenant bleed, customer data as demo content, personal life as
  company context, employee notes as HR decisions, inferred sensitive
  attributes as output, embedding leaks, vector-neighbor leaks, and
  confidential source text sent to untrusted models.

`super-ontology-strategic-incentive-compatibility.json`

- Public-safe strategic incentive compatibility seed.
- Requires KPI reports, commissions, approvals, customer ratings, benchmark
  scores, agent votes, vendor claims, access requests, social pressure,
  family pressure, data-payment claims, and cost-saving claims to name the
  principal, agent, private information, objective, payoff or reward model,
  conflict disclosure, strategic behavior hypothesis, counterfactual
  truthfulness check, holdout or audit sample, independent verification,
  collusion check, mechanism constraint, counter-incentive, appeal path, audit,
  rollback, and residual incentive risk before authority-bearing use.
- Keeps `runtimePromotionAllowed=false` on export.
- Blocks self-report as truth, KPI as objective, commission reports as facts,
  manager approval as no conflict, vendor claims as source quality, customer
  ratings as value, agent votes as independence, benchmark score as general
  capability, cheap provider as best provider, compliance attestation as
  compliance, hidden affiliation as neutral review, retention as satisfaction,
  family pressure as user preference, collusive agents as quorum, missing
  mechanism review as runtime write, and reward model as human goal.

`super-ontology-reflexive-feedback-stability.json`

- Public-safe reflexive feedback stability seed.
- Requires post-intervention observations, recommendation effects, route
  distributions, dashboard movement, repeated retrieval, generated artifacts,
  model output reuse, agent self-scores, market responses, social contagion,
  scheduler replays, and adapted user behavior to name intervention id,
  pre-intervention baseline, feedback path, time lag, holdout or
  counterfactual, real-world anchor, synthetic-data ratio, stability margin,
  damping or rate limit, saturation bound, externality map, affected
  stakeholders, monitoring trace, stop condition, rollback, owner review, and
  residual feedback risk before authority-bearing use.
- Keeps `runtimePromotionAllowed=false` on export.
- Blocks observation after intervention as neutral truth, recommendation effect
  as preference, self-generated content as training data, model output as
  source corpus, dashboard change as system improvement, repeated retrieval as
  relevance, agent self-score as external feedback, closed loop without
  counterfactual, runaway feedback as runtime write, oscillation as adaptation,
  delayed harm ignored, synthetic-data loop as real distribution, intervention
  without stop condition, user adaptation as stable preference, market response
  as causal truth, personal nudge as identity change, and feedback loop as
  memory or policy write.

## Default State

Every exported Super Ontology contract starts as:

```text
state = candidate
runtimeGraphWriteEnabled = false
zeroErrorClaim = false
shadowRequired = true
canaryRequiredForMixedContext = true
rollbackRequired = true
openWorldCoverageRequired = true
unknownCombinationRuntimeWritesBlocked = true
uncoveredModalityRuntimeWritesBlocked = true
consensusCoordinationRequired = true
agentAgreementRuntimeWritesBlocked = true
majorityVoteRuntimeWritesBlocked = true
splitBrainRuntimeWritesBlocked = true
taskCoverageRequired = true
contextualFlowRequired = true
causalImpactRequired = true
assuranceCaseRequired = true
knowledgeHomeostasisRequired = true
adversarialProvenanceRequired = true
epistemicCalibrationRequired = true
semanticAlignmentRequired = true
resilienceControlRequired = true
invariantVerificationRequired = true
observabilityTelemetryRequired = true
objectiveProxyValidityRequired = true
stakeholderPreferenceGovernanceRequired = true
normativeAuthorityDriftRequired = true
sideEffectContainmentRequired = true
irreversibleRuntimeActionsBlocked = true
idempotencyKeyRequired = true
compensationPlanRequired = true
sourceLineageVersionRequired = true
unversionedSourceRuntimeWritesBlocked = true
derivedArtifactPromotionBlocked = true
lineageRepairRequired = true
entityIdentityResolutionRequired = true
ambiguousIdentityRuntimeWritesBlocked = true
identityMergeReviewRequired = true
identityRollbackRequired = true
temporalStateTransitionRequired = true
timelessStateRuntimeWritesBlocked = true
eventReplayRequired = true
projectionVersionRequired = true
capabilityDelegationAuthorityRequired = true
unscopedCapabilityRuntimeWritesBlocked = true
delegationChainRequired = true
capabilityAttenuationRequired = true
purposeBoundCapabilityRequired = true
privacyConfidentialityBoundaryRequired = true
unclassifiedPrivateRuntimeWritesBlocked = true
privacyBoundaryReviewRequired = true
publicTrainingDisclosureFlagRequired = true
deletionAndRetentionStateRequired = true
crossTenantPrivacyBleedBlocked = true
strategicIncentiveCompatibilityRequired = true
incentiveConflictRuntimeWritesBlocked = true
mechanismReviewRequired = true
independentVerificationRequired = true
collusionCheckRequired = true
mechanismRedesignRequired = true
reflexiveFeedbackStabilityRequired = true
postInterventionRuntimeWritesBlocked = true
feedbackHoldoutRequired = true
realWorldAnchorRequired = true
dampingAndStopConditionRequired = true
modelCollapseLoopBlocked = true
memoryCuratorBridgeRequired = true
directDurableMemoryWritesBlocked = true
untrustedSourceRuntimeWritesBlocked = true
uncalibratedRuntimeWritesBlocked = true
highAuthorityAlignmentReviewRequired = true
unreviewedSemanticRuntimeWritesBlocked = true
degradedRuntimeWritesBlocked = true
emergencyStopBypassBlocked = true
runtimeInvariantWritesBlocked = true
forbiddenTransitionBlocked = true
unobservableRuntimeWritesBlocked = true
proxyOptimizationRuntimeWritesBlocked = true
singleStakeholderRuntimeWritesBlocked = true
aggregationRuleRequired = true
appealPathRequired = true
stalePolicyRuntimeWritesBlocked = true
jurisdictionScopeRequired = true
authorityHierarchyRequired = true
```

The package can be searched, reviewed, and replayed. It cannot write official
knowledge, mutate runtime memory, or authorize tools by itself.

## Required Pipeline

The public contract names these layers:

1. source intake,
2. evidence packet,
3. belief ledger,
4. knowledge capsule,
5. affordance action binding,
6. open-world coverage contract,
7. consensus coordination contract,
8. task coverage contract,
9. contextual flow contract,
10. causal impact contract,
11. assurance case contract,
12. knowledge homeostasis contract,
13. adversarial provenance contract,
14. epistemic calibration contract,
15. semantic alignment contract,
16. resilience control contract,
17. invariant verification contract,
18. observability telemetry contract,
19. objective proxy validity contract,
20. stakeholder preference governance contract,
21. normative authority drift contract,
22. side-effect containment contract,
23. source lineage version contract,
24. entity identity resolution contract,
25. temporal state transition contract,
26. capability delegation authority contract,
27. privacy confidentiality boundary contract,
28. strategic incentive compatibility contract,
29. reflexive feedback stability contract,
30. Agentlas integration contract,
31. Memory Curator bridge,
32. promotion readiness,
33. promotion replay drill,
34. architecture sync review.

## Hard Stops

Automatic promotion is blocked when:

- a candidate claims zero-error or universal completeness;
- a raw source would write directly into an ontology;
- a graph edge joins forbidden personal/company/public contexts;
- a downstream agent receives the whole graph instead of a task capsule;
- a tool call lacks argument provenance or user authority;
- a proposal/deck fixture is treated as proof that all future work is covered;
- a new world, task, modality, fault, authority, or write-surface combination
  would proceed without open-world fixture pressure, shadow replay, owner
  review, or sync review;
- a requested task family, affordance type, evidence mode, or rollback path is
  missing;
- a relation would be treated as causation, action permission, or intervention
  authority without counterfactual checks, blast radius, observability, and
  rollback;
- a broad claim lacks an assurance case, observed evidence, validator, residual
  risk, or rollback plan;
- a knowledge health signal overruns its error budget but still continues;
- a critical homeostasis row would allow direct runtime writes;
- a privacy incident would public-export or write memory without quarantine;
- stale, parser-failed, or runtime-desynced knowledge would be treated as
  current operational truth;
- prompt injection, poisoned source, spoofed citation, forged provenance,
  hidden OCR text, tool-output tampering, or stale trusted-source replay would
  become retrieval, memory, tool, or public seed authority;
- missing evidence, conflicting sources, stale evidence, low retrieval
  relevance, model disagreement, or unknown epistemic state would become a
  confident answer, graph write, tool action, memory write, or public artifact;
- a regulated answer, financial estimate, scientific claim, physical action, or
  route sync has an uncalibrated confidence band or wide judge interval;
- a same label, similar embedding, generated label, OCR label, route label,
  abbreviation, or unit label would become an exact/equivalent/same-individual
  relation, graph edge, memory merge, or public artifact without scope,
  validation, owner review, diff, and rollback;
- validator disagreement, retrieval drift, semantic regression, provenance
  gaps, Memory Curator backlog, tool error spikes, unknown task families,
  context-flow violations, sync drift, degraded parser/sensor signals, rollback
  failure, or emergency-stop bypass would keep nominal graph, memory, tool,
  route, release, or public-artifact authority;
- memory writes, graph writes, tool calls, public exports, route sync, release
  seeds, rollback, or emergency-stop transitions bypass their event-stream
  invariants;
- graph, memory, tool, public, route, release, repair, rollback, or stop events
  lack trace/span/correlation/audit telemetry, redaction and retention policy,
  required snapshots, alert refs, or rollback refs;
- objective/proxy validity evidence, construct definition, stakeholder map,
  countermetric, negative control, gaming probe, benchmark provenance,
  longitudinal check, owner review, or rollback plan is missing for
  metric-driven graph, memory, tool, route, release, or public writes;
- metric improvement, approval rate, open rate, benchmark score, test pass
  rate, ontology edge count, self-judge score, short-term profit, cost savings,
  green dashboards, reward deltas, or label-leaked accuracy are treated as
  success without proving they measure the intended construct;
- owner preference, majority vote, ranking, behavior signal, role power, old
  preference record, or strategic preference report is treated as legitimate
  write authority without stakeholder map, scope of authority, aggregation
  rule, consent or rights checks, dissent capture, appeal path, review owner,
  and rollback;
- stale policy, wrong jurisdiction, draft policy, superseded contract, expired
  consent, local custom, policy translation, regulation summary, license
  conflict, retention gap, cross-border transfer, emergency exception without
  expiry, or legal/compliance claim is treated as current authority without
  primary source, effective date, version, scope, precedence rule, review owner,
  audit trail, and rollback;
- a self-report, KPI, commission report, approval chain, customer rating,
  benchmark score, agent vote, vendor label, cost-saving claim, compliance
  attestation, survey response, retention metric, access request, social
  pressure, hidden affiliation, strategic silence, or collusive quorum is
  treated as truth without incentive evidence, independent verification,
  collusion checks, mechanism constraints, appeal path, audit trail, and
  rollback;
- a post-intervention observation, recommendation effect, dashboard movement,
  repeated retrieval, generated artifact, model output reuse, agent self-score,
  market response, social contagion, scheduler replay, or adapted user behavior
  is treated as neutral truth without intervention id, baseline, feedback path,
  lag window, holdout or counterfactual, real-world anchor, stability margin,
  damping, stop condition, monitoring, and rollback;
- an AppBridge route output would be treated as source-write authority;
- a release artifact lacks SLSA or in-toto style provenance;
- AppBridge is treated as source of truth;
- a candidate bypasses the Memory Curator bridge and writes durable memory
  directly;
- a memory candidate stores raw prompt, private path, or secret-like material;
- rollback is missing;
- live shadow/canary evidence is missing for runtime behavior.

## Runtime Boundary

Public core defines the contract. Hosted Web may emit it in ZIP exports.
Desktop and terminal may seed it locally, but only as candidate metadata until
local policy approves a later phase.

This contract came from the Super Ontology Architect research. Treat it as
evaluation and governance infrastructure first. Do not claim production
omniscience or first-class runtime behavior from export metadata alone.
