Skip to content

Latest commit

 

History

History
34 lines (27 loc) · 1.46 KB

CLAIMS.md

File metadata and controls

34 lines (27 loc) · 1.46 KB

Claims Register

Permitted design statements at bootstrap

  • OIC is designed to convert heterogeneous institutional documents into source-anchored candidate controls.
  • OIC separates extracted or inferred meaning from institutionally admitted meaning.
  • OIC defines a target-independent Open Control Envelope as its proposed enforcement boundary.
  • OIC is designed to preserve unresolved ambiguity and explicit CANNOT outcomes.
  • The open repository and hosted Lab are required to use the same semantic compiler core.

These are architecture statements, not measured quality claims.

Claims requiring frozen evidence

  • Source-supported executable-field percentage.
  • Normative field accuracy.
  • Authority reconstruction accuracy.
  • Ambiguity recall and false-resolution rate.
  • Runtime behavioral conformance.
  • Change-impact recall.
  • Practitioner review-time reduction.
  • Comparative outperformance against a named baseline.

Forbidden at current status

  • OIC guarantees legal or regulatory compliance.
  • OIC eliminates legal, policy, compliance, audit, or authorized human review.
  • OIC autonomously determines correct institutional meaning.
  • OIC is enterprise-ready.
  • OIC is universally the first or best institutional compiler.
  • OIC outperforms all rules-as-code, GRC, policy, or agent-governance systems.
  • ZTL proves source authority or institutional legitimacy.
  • VEIP creates policy meaning or authority.
  • A compiled control is valid merely because it passes tests.