24 Ontology.Reasoning - Varietyz/Disciplined-AI-Software-Development GitHub Wiki

Reasoning β€” Ontology β€” Bane's Lab

Every algorithm grammar is an instance of the derivation loop, which has ten stages, each on one reasoning axis, joined by transitions that sequence, gate or…

Canonical: https://banes-lab.com/ontology/reasoning

The Ontology

The ontology is a queryable canon of software architecture. It holds every principle with its relations and its repair, every term with its definition, every algorithm with its contract, the reasoning that derives them, the layers they live in and how every tension between them is resolved, and every reference from one record to another is a link.

Reasoning

594 of 594 shown

Sections

The derivation loop

Every algorithm grammar is an instance of the derivation loop, which has ten stages, each on one reasoning axis, joined by transitions that sequence, gate or refute back. Each stage is listed with the contracts that run at it and the records it grounds, and the traversal is taught in the loop on the methodology page.

How it is checked

Checked by

the reasoning-native check, which requires every process grammar's kernel to map the loop's stages and every staged record to name a real stage and that stage's axis

Population

Every process grammar, its kernel and its staged records

Freshness

A verdict stands until the loop, a grammar or a staged record changes

Refusal

The gate fails on an unknown stage, a stage whose axis does not match, or a kernel that omits the verify stage

Observation

None, because the loop is a procedure the grammars instantiate, and nothing observes it while a run executes

Evidence

Watched to fire and to accept: a suite plants an unknown stage, a mismatched axis and a kernel that omits the verify stage, and passes a fully typed staged record

Authoritative side

The loop's stage list, which every kernel and staged record cites

Depends on

Not answered

Shape it refuses

Not answered

Relations diagram

The derivation loop with its gates.

flowchart TB
    n_orient["orient Β· ontology"]
    n_intent["intent Β· teleology"]
    n_see["see Β· analysis"]
    n_derive["derive Β· reasoning"]
    n_project["project Β· reasoning"]
    n_act["act Β· formalization"]
    n_constrain["constrain Β· teleology"]
    n_verify["verify Β· verification"]
    n_commit["commit Β· representation"]
    n_terminate["terminate Β· termination"]
    n_orient --> n_intent
    n_intent -- tel-priority --> n_see
    n_see --> n_derive
    n_derive --> n_project
    n_project --> n_act
    n_act --> n_constrain
    n_constrain --> n_verify
    n_verify -.-> n_derive
    n_verify --> n_commit
    n_commit --> n_terminate
    n_terminate --> n_orient

orient

Details

Contracts Evidence-Before-Generation, Semantic Operation Boundary, Capability Profile, Domain Cache Validation, Scope Extraction, Domain Knowledge Base, DSL Compliance Loading, Workspace Configuration Discovery, Runtime-Neutral Automation Boundary, Capability Degradation, Automation Opportunity Detection, Runtime-Agnostic Adapter Boundary, Capability Disclosure, Iterative Variation Discovery, Detection Registry, Orientation Stage, Authoritative Source Loading, Trust Anchor, Intent & Directionality Normalization, Skeptical Context Acquisition, Dynamic Discovery Pattern Generation, Context Initialization, Trust Anchor Declaration, Coverage Workspace, PAG Document Declaration, Analysis Workspace, Registry Baseline, Profile Compose, Seed Composition, Taxonomy Jurisdiction

How it is checked

Checked by the reasoning-native check, which requires every process grammar's kernel to map the loop's stages and every staged record to name a real stage and that stage's axis

Population Every process grammar, its kernel and its staged records

Freshness A verdict stands until the loop, a grammar or a staged record changes

Refusal The gate fails on an unknown stage, a stage whose axis does not match, or a kernel that omits the verify stage

Observation None, because the loop is a procedure the grammars instantiate, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants an unknown stage, a mismatched axis and a kernel that omits the verify stage, and passes a fully typed staged record

Authoritative side The loop's stage list, which every kernel and staged record cites

Depends on Not answered

Shape it refuses Not answered

intent

Details

Contracts Adaptive Phase Boundary, Static-to-Dynamic Readiness, Automation Priority Ordering, Canonical Variation Selection, Developer Decision Gate, Teleological Intent Gate, Severity-Ordered Remediation, Coverage Risk Prioritization, Anti-Pattern Priority Matrix, Reshape Risk Priority

How it is checked

Checked by the reasoning-native check, which requires every process grammar's kernel to map the loop's stages and every staged record to name a real stage and that stage's axis

Population Every process grammar, its kernel and its staged records

Freshness A verdict stands until the loop, a grammar or a staged record changes

Refusal The gate fails on an unknown stage, a stage whose axis does not match, or a kernel that omits the verify stage

Observation None, because the loop is a procedure the grammars instantiate, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants an unknown stage, a mismatched axis and a kernel that omits the verify stage, and passes a fully typed staged record

Authoritative side The loop's stage list, which every kernel and staged record cites

Depends on Not answered

Shape it refuses Not answered

see

Details

Contracts Non-Destructive Domain Investigation, Risk Complexity Reversibility, Existing Pattern Extraction, Knowledge Documentation Relevance, Breaking Point Calculation, Convention Strength Analysis, Scalability Projection, Research Guidance, Tool Calibration, Lifetime Resolution, Surface Grid Walk, PAG Keyword Ontology, Compliance Gap, Semantic Domain Partitioning, Behavioral Signature Extraction, Cross-Class Pattern Detection, Behavioral Inconsistency, Sequential Chain Duplication, Temporal Coupling Detection, Relational Graph Duplication, Causal Wiring Duplication, Anomaly Outlier Detection, Conceptual Duplication Detection, Fractal Scale Duplication, Path Role Walk

How it is checked

Checked by the reasoning-native check, which requires every process grammar's kernel to map the loop's stages and every staged record to name a real stage and that stage's axis

Population Every process grammar, its kernel and its staged records

Freshness A verdict stands until the loop, a grammar or a staged record changes

Refusal The gate fails on an unknown stage, a stage whose axis does not match, or a kernel that omits the verify stage

Observation None, because the loop is a procedure the grammars instantiate, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants an unknown stage, a mismatched axis and a kernel that omits the verify stage, and passes a fully typed staged record

Authoritative side The loop's stage list, which every kernel and staged record cites

Depends on Not answered

Shape it refuses Not answered

derive

Details

Contracts Principle Extraction, Hybrid Workflow Orchestration, Context Forking Configuration, Verb-Based Execution Classification, Workflow Type Document Selection, Workflow Principles Mapping, Intentional Static Separation, Extension Interface Discovery, Pattern Classification, Refactor Intent Classification, Architecture Compliance Targeting, Existing Solution Conflict, Planning Stage, Principle Activation, Protocol Semantic Selection, Violation Classification, Invocation Join, Duplicate Disposition Walk, Uncovered Gap Derivation, PAG Ambiguity Reduction, Anti-Pattern Classification, Abstraction Boundary Principle, Base-Class Candidate Selection, Canonical Config Resolution, Concern Classification, Container Ladder, Export Triage Ladder

How it is checked

Checked by the reasoning-native check, which requires every process grammar's kernel to map the loop's stages and every staged record to name a real stage and that stage's axis

Population Every process grammar, its kernel and its staged records

Freshness A verdict stands until the loop, a grammar or a staged record changes

Refusal The gate fails on an unknown stage, a stage whose axis does not match, or a kernel that omits the verify stage

Observation None, because the loop is a procedure the grammars instantiate, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants an unknown stage, a mismatched axis and a kernel that omits the verify stage, and passes a fully typed staged record

Authoritative side The loop's stage list, which every kernel and staged record cites

Depends on Not answered

Shape it refuses Not answered

project

Details

Contracts Phase Validation Requirement, Validation Strategy Composition, Agent Sequence Definition, Four-Dimensional Agent Graph, Performance-Aware Discovery Design, Dynamic Extension Architecture, Migration Action Mapping, Atomic Refactor Phase, Phase Decomposition, Four-Dimensional Phase Graph, Dependency Linearization, Severity Assignment, Loop Class Labeling, Technique and Invariant Selection, PAG Node Decomposition, PAG Structure Declaration, Concrete-vs-Abstract Responsibility Split, Template Method Lifecycle, Migration Ordering, Stage Ordering, Name Projection, Dialect Resolution

How it is checked

Checked by the reasoning-native check, which requires every process grammar's kernel to map the loop's stages and every staged record to name a real stage and that stage's axis

Population Every process grammar, its kernel and its staged records

Freshness A verdict stands until the loop, a grammar or a staged record changes

Refusal The gate fails on an unknown stage, a stage whose axis does not match, or a kernel that omits the verify stage

Observation None, because the loop is a procedure the grammars instantiate, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants an unknown stage, a mismatched axis and a kernel that omits the verify stage, and passes a fully typed staged record

Authoritative side The loop's stage list, which every kernel and staged record cites

Depends on Not answered

Shape it refuses Not answered

act

Details

Contracts Portable Contract Composition, Adapter Rendering, Agent Workflow File Modification Recovery, Shared Document Workspace, Agent Document Responsibility, Agent Activation Invocation, Parallel Batch Execution, Sequential Agent Execution, Handoff Signal, Orchestrator Action, Workflow Coordination Sequence, Workflow Recovery Loop, Checklist Integration, Phase Documentation Template, Capability Invocation Protocol, Centralized Reference Resolver, Cache Invalidation Strategy, Manual Fallback Preservation, Dynamic Failure Isolation, Entry Point Migration, Knowledge Capture, Replacement Refactor, Rollback-Centered Execution, Compilation Stage, Codebase Pattern Enforcement, Verb Template Binding, Task Atomization, Ripple Chain Analysis, Validator Coverage, Structured Observability Context, Cross-Cutting Surface Coverage, Legacy Elimination, Hierarchical Numbering, File-Scoped Fix, File Limit Remediation, Import Boundary Remediation, Naming Convention Remediation, Base-Class Compliance Remediation, CSS Token Remediation, DOM Factory Remediation, Console Usage Remediation, Lifecycle Symmetry Remediation, Stylelint Post-Fix, File Modification Recovery, Defensive String Normalization, Safe Arithmetic Contract, Recursion Control, Advanced Tool Escalation, Test Authoring, PAG Explicit Control Flow, PAG Semantic Operation, Base Schematic Composition, Backup-Verified Migration, Registry Regeneration, Anti-Reintroduction Gate, Idempotent Merge, Deterministic Merge Core, Persistence Fork, Comment Normalization Remediation, Custom-Rule Derivation, Composed Turn Contract, Container Reshape

How it is checked

Checked by the reasoning-native check, which requires every process grammar's kernel to map the loop's stages and every staged record to name a real stage and that stage's axis

Population Every process grammar, its kernel and its staged records

Freshness A verdict stands until the loop, a grammar or a staged record changes

Refusal The gate fails on an unknown stage, a stage whose axis does not match, or a kernel that omits the verify stage

Observation None, because the loop is a procedure the grammars instantiate, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants an unknown stage, a mismatched axis and a kernel that omits the verify stage, and passes a fully typed staged record

Authoritative side The loop's stage list, which every kernel and staged record cites

Depends on Not answered

Shape it refuses Not answered

constrain

Details

Contracts Creation History Collision, Replacement Safety, Automation Operation Mode, Operation Mode Gating, Admissibility Constraint Gate, Phase-Separated Execution, PAG Invariant Record, Boundary Reconciliation, Vocabulary Admission Gate

Grounds Governed Autonomous Plan Loop

How it is checked

Checked by the reasoning-native check, which requires every process grammar's kernel to map the loop's stages and every staged record to name a real stage and that stage's axis

Population Every process grammar, its kernel and its staged records

Freshness A verdict stands until the loop, a grammar or a staged record changes

Refusal The gate fails on an unknown stage, a stage whose axis does not match, or a kernel that omits the verify stage

Observation None, because the loop is a procedure the grammars instantiate, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants an unknown stage, a mismatched axis and a kernel that omits the verify stage, and passes a fully typed staged record

Authoritative side The loop's stage list, which every kernel and staged record cites

Depends on Not answered

Shape it refuses Not answered

verify

Details

Contracts Semantic Compliance Validation, Evidence Grounding Validation, Algorithmic Embodiment Validation, Workflow Validation Gate, Measured-vs-Estimated Validation, Architecture Validation Before Persistence, Additive Debt Gate, Pattern-Specific Validation, Zero-Duplication Verification, Validation Score, Validation Stage, Semantic Debt Policy, Evidence-Based Claim Verification, Validation Suite Battery, Repair Stage, Bounded Repair Loop, Severity Failure Routing, Verification Loop, Verification Execution, Reverification Gate, Evidence-Gated Claim Verification, Environment Capability Verification, Behavioral Self-Test, Adversarial Input Testing, Recursive Self-Verification, Evidence Verdict, PAG Handoff Gate, Anti-Pattern Elimination Verification, Distillation Metrics, Delta Capture, Plan Phase Verification, Machine Verdict Derivation, Mode Contract Validation, Discovery Verification, Alignment Cadence

How it is checked

Checked by the reasoning-native check, which requires every process grammar's kernel to map the loop's stages and every staged record to name a real stage and that stage's axis

Population Every process grammar, its kernel and its staged records

Freshness A verdict stands until the loop, a grammar or a staged record changes

Refusal The gate fails on an unknown stage, a stage whose axis does not match, or a kernel that omits the verify stage

Observation None, because the loop is a procedure the grammars instantiate, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants an unknown stage, a mismatched axis and a kernel that omits the verify stage, and passes a fully typed staged record

Authoritative side The loop's stage list, which every kernel and staged record cites

Depends on Not answered

Shape it refuses Not answered

commit

Details

Contracts Audit Artifact, Final Generation Report, Template Assembly, Automation Session Report, Centralization Report, Rendering Stage, Checklist Output Rendering, Partial Success Reporting, Completion Report, Investigation Report, Action Log, Convergence Walk, Coverage Ledger, Pattern Distillation History, Version Provenance, Living Plan State, Versioned Turn Provenance, Taxonomy Ledger

How it is checked

Checked by the reasoning-native check, which requires every process grammar's kernel to map the loop's stages and every staged record to name a real stage and that stage's axis

Population Every process grammar, its kernel and its staged records

Freshness A verdict stands until the loop, a grammar or a staged record changes

Refusal The gate fails on an unknown stage, a stage whose axis does not match, or a kernel that omits the verify stage

Observation None, because the loop is a procedure the grammars instantiate, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants an unknown stage, a mismatched axis and a kernel that omits the verify stage, and passes a fully typed staged record

Authoritative side The loop's stage list, which every kernel and staged record cites

Depends on Not answered

Shape it refuses Not answered

terminate

Details

Contracts Agent Generation Completion, First-Time Initiation, Automation Completion Status, Completion Truthfulness, Explicit Termination, Early Success Exit, Iteration Bound, Validation Gate, Coverage Completion, PAG Well-Formedness Validation, Pattern Distillation Completion Truthfulness, Phase Close Gate, Bounded Cascade Termination, Taxonomy Completion

How it is checked

Checked by the reasoning-native check, which requires every process grammar's kernel to map the loop's stages and every staged record to name a real stage and that stage's axis

Population Every process grammar, its kernel and its staged records

Freshness A verdict stands until the loop, a grammar or a staged record changes

Refusal The gate fails on an unknown stage, a stage whose axis does not match, or a kernel that omits the verify stage

Observation None, because the loop is a procedure the grammars instantiate, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants an unknown stage, a mismatched axis and a kernel that omits the verify stage, and passes a fully typed staged record

Authoritative side The loop's stage list, which every kernel and staged record cites

Depends on Not answered

Shape it refuses Not answered

orient β†’ intent

Details

orient β†’ intent Β· Transition: sequences

intent β†’ see

Details

intent β†’ see Β· Transition: gates Β· Gate: tel-priority Β· On fail: redirect

see β†’ derive

Details

see β†’ derive Β· Transition: sequences

derive β†’ project

Details

derive β†’ project Β· Transition: sequences

project β†’ act

Details

project β†’ act Β· Transition: sequences

act β†’ constrain

Details

act β†’ constrain Β· Transition: sequences

constrain β†’ verify

Details

constrain β†’ verify Β· Transition: sequences

verify β†’ derive

Details

verify β†’ derive Β· Transition: refutes-back Β· Gate: ver-evidence Β· On fail: derive

verify β†’ commit

Details

verify β†’ commit Β· Transition: sequences

commit β†’ terminate

Details

commit β†’ terminate Β· Transition: sequences

terminate β†’ orient

Details

terminate β†’ orient Β· Transition: sequences Β· Gate: ter-stop Β· On pass: stop

The substrate

Beneath the loop lies the generative substrate, meaning the cycle every node passes through, the recursion that turns emergence back into a new difference, and the math types each node yields.

Recursion Β· emergence β†’ difference

Relations diagram

The substrate cycle and its recursion.

flowchart LR
    n_existence["existence"]
    n_difference["difference"]
    n_relation["relation"]
    n_structure["structure"]
    n_transformation["transformation"]
    n_constraint["constraint"]
    n_emergence["emergence"]
    n_existence --> n_difference
    n_difference --> n_relation
    n_relation --> n_structure
    n_structure --> n_transformation
    n_transformation --> n_constraint
    n_constraint --> n_emergence
    n_emergence -.-> n_difference

Existence

Details

How it is checked

Checked by the ontology resolution gate over every model step, math type, genesis tag and construct that names a substrate node

Population Every model, document construct and genesis tag that names the substrate node

Freshness A verdict stands until the substrate or a record that names one of its nodes changes

Refusal The gate fails on a reference to a substrate node that does not exist

Observation None, because a substrate node is a primitive of pattern formation, and nothing observes it while a run executes

Evidence Watched to fire and to accept: one suite plants a step outside its model's step kind, another plants a ground whose kind exists and whose id does not, and the bundled data validates clean

Authoritative side The substrate node list, which every step, math type, tag and construct that names a node cites

Depends on Not answered

Shape it refuses Not answered

Difference

Details

How it is checked

Checked by the ontology resolution gate over every model step, math type, genesis tag and construct that names a substrate node

Population Every model, document construct and genesis tag that names the substrate node

Freshness A verdict stands until the substrate or a record that names one of its nodes changes

Refusal The gate fails on a reference to a substrate node that does not exist

Observation None, because a substrate node is a primitive of pattern formation, and nothing observes it while a run executes

Evidence Watched to fire and to accept: one suite plants a step outside its model's step kind, another plants a ground whose kind exists and whose id does not, and the bundled data validates clean

Authoritative side The substrate node list, which every step, math type, tag and construct that names a node cites

Depends on Not answered

Shape it refuses Not answered

Relation

Details

How it is checked

Checked by the ontology resolution gate over every model step, math type, genesis tag and construct that names a substrate node

Population Every model, document construct and genesis tag that names the substrate node

Freshness A verdict stands until the substrate or a record that names one of its nodes changes

Refusal The gate fails on a reference to a substrate node that does not exist

Observation None, because a substrate node is a primitive of pattern formation, and nothing observes it while a run executes

Evidence Watched to fire and to accept: one suite plants a step outside its model's step kind, another plants a ground whose kind exists and whose id does not, and the bundled data validates clean

Authoritative side The substrate node list, which every step, math type, tag and construct that names a node cites

Depends on Not answered

Shape it refuses Not answered

Structure

Details

How it is checked

Checked by the ontology resolution gate over every model step, math type, genesis tag and construct that names a substrate node

Population Every model, document construct and genesis tag that names the substrate node

Freshness A verdict stands until the substrate or a record that names one of its nodes changes

Refusal The gate fails on a reference to a substrate node that does not exist

Observation None, because a substrate node is a primitive of pattern formation, and nothing observes it while a run executes

Evidence Watched to fire and to accept: one suite plants a step outside its model's step kind, another plants a ground whose kind exists and whose id does not, and the bundled data validates clean

Authoritative side The substrate node list, which every step, math type, tag and construct that names a node cites

Depends on Not answered

Shape it refuses Not answered

Transformation

Details

How it is checked

Checked by the ontology resolution gate over every model step, math type, genesis tag and construct that names a substrate node

Population Every model, document construct and genesis tag that names the substrate node

Freshness A verdict stands until the substrate or a record that names one of its nodes changes

Refusal The gate fails on a reference to a substrate node that does not exist

Observation None, because a substrate node is a primitive of pattern formation, and nothing observes it while a run executes

Evidence Watched to fire and to accept: one suite plants a step outside its model's step kind, another plants a ground whose kind exists and whose id does not, and the bundled data validates clean

Authoritative side The substrate node list, which every step, math type, tag and construct that names a node cites

Depends on Not answered

Shape it refuses Not answered

Constraint

Details

How it is checked

Checked by the ontology resolution gate over every model step, math type, genesis tag and construct that names a substrate node

Population Every model, document construct and genesis tag that names the substrate node

Freshness A verdict stands until the substrate or a record that names one of its nodes changes

Refusal The gate fails on a reference to a substrate node that does not exist

Observation None, because a substrate node is a primitive of pattern formation, and nothing observes it while a run executes

Evidence Watched to fire and to accept: one suite plants a step outside its model's step kind, another plants a ground whose kind exists and whose id does not, and the bundled data validates clean

Authoritative side The substrate node list, which every step, math type, tag and construct that names a node cites

Depends on Not answered

Shape it refuses Not answered

Invariant

Details

How it is checked

Checked by the ontology resolution gate over every model step, math type, genesis tag and construct that names a substrate node

Population Every model, document construct and genesis tag that names the substrate node

Freshness A verdict stands until the substrate or a record that names one of its nodes changes

Refusal The gate fails on a reference to a substrate node that does not exist

Observation None, because a substrate node is a primitive of pattern formation, and nothing observes it while a run executes

Evidence Watched to fire and to accept: one suite plants a step outside its model's step kind, another plants a ground whose kind exists and whose id does not, and the bundled data validates clean

Authoritative side The substrate node list, which every step, math type, tag and construct that names a node cites

Depends on Not answered

Shape it refuses Not answered

Uncertainty

Details

How it is checked

Checked by the ontology resolution gate over every model step, math type, genesis tag and construct that names a substrate node

Population Every model, document construct and genesis tag that names the substrate node

Freshness A verdict stands until the substrate or a record that names one of its nodes changes

Refusal The gate fails on a reference to a substrate node that does not exist

Observation None, because a substrate node is a primitive of pattern formation, and nothing observes it while a run executes

Evidence Watched to fire and to accept: one suite plants a step outside its model's step kind, another plants a ground whose kind exists and whose id does not, and the bundled data validates clean

Authoritative side The substrate node list, which every step, math type, tag and construct that names a node cites

Depends on Not answered

Shape it refuses Not answered

Information

Details

How it is checked

Checked by the ontology resolution gate over every model step, math type, genesis tag and construct that names a substrate node

Population Every model, document construct and genesis tag that names the substrate node

Freshness A verdict stands until the substrate or a record that names one of its nodes changes

Refusal The gate fails on a reference to a substrate node that does not exist

Observation None, because a substrate node is a primitive of pattern formation, and nothing observes it while a run executes

Evidence Watched to fire and to accept: one suite plants a step outside its model's step kind, another plants a ground whose kind exists and whose id does not, and the bundled data validates clean

Authoritative side The substrate node list, which every step, math type, tag and construct that names a node cites

Depends on Not answered

Shape it refuses Not answered

Procedure

Details

How it is checked

Checked by the ontology resolution gate over every model step, math type, genesis tag and construct that names a substrate node

Population Every model, document construct and genesis tag that names the substrate node

Freshness A verdict stands until the substrate or a record that names one of its nodes changes

Refusal The gate fails on a reference to a substrate node that does not exist

Observation None, because a substrate node is a primitive of pattern formation, and nothing observes it while a run executes

Evidence Watched to fire and to accept: one suite plants a step outside its model's step kind, another plants a ground whose kind exists and whose id does not, and the bundled data validates clean

Authoritative side The substrate node list, which every step, math type, tag and construct that names a node cites

Depends on Not answered

Shape it refuses Not answered

Emergence

Details

How it is checked

Checked by the ontology resolution gate over every model step, math type, genesis tag and construct that names a substrate node

Population Every model, document construct and genesis tag that names the substrate node

Freshness A verdict stands until the substrate or a record that names one of its nodes changes

Refusal The gate fails on a reference to a substrate node that does not exist

Observation None, because a substrate node is a primitive of pattern formation, and nothing observes it while a run executes

Evidence Watched to fire and to accept: one suite plants a step outside its model's step kind, another plants a ground whose kind exists and whose id does not, and the bundled data validates clean

Authoritative side The substrate node list, which every step, math type, tag and construct that names a node cites

Depends on Not answered

Shape it refuses Not answered

The reasoning layers

The reasoning axes are arranged on these layers, each listed with the question it answers and the axes it holds.

Substrate

Details

Question How does anything come to be?

How it is checked

Checked by the ontology resolution gate, which requires every axis and substrate node that names a layer to resolve

Population Every axis and substrate node that names the layer

Freshness A verdict stands until the layer list or a record that names a layer changes

Refusal The gate fails on an axis or substrate node that names a layer that does not exist

Observation None, because a layer is a grouping of axes, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants an axis that names a missing layer, and the bundled references resolve

Authoritative side The layer list, which every axis and substrate node that names a layer cites

Depends on Not answered

Shape it refuses Not answered

Epistemic

Details

Question How is it known?

Axes ontology, analysis, reasoning, representation, formalization

How it is checked

Checked by the ontology resolution gate, which requires every axis and substrate node that names a layer to resolve

Population Every axis and substrate node that names the layer

Freshness A verdict stands until the layer list or a record that names a layer changes

Refusal The gate fails on an axis or substrate node that names a layer that does not exist

Observation None, because a layer is a grouping of axes, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants an axis that names a missing layer, and the bundled references resolve

Authoritative side The layer list, which every axis and substrate node that names a layer cites

Depends on Not answered

Shape it refuses Not answered

Conative

Details

Question What is worth doing?

Axes teleology

How it is checked

Checked by the ontology resolution gate, which requires every axis and substrate node that names a layer to resolve

Population Every axis and substrate node that names the layer

Freshness A verdict stands until the layer list or a record that names a layer changes

Refusal The gate fails on an axis or substrate node that names a layer that does not exist

Observation None, because a layer is a grouping of axes, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants an axis that names a missing layer, and the bundled references resolve

Authoritative side The layer list, which every axis and substrate node that names a layer cites

Depends on Not answered

Shape it refuses Not answered

Evaluative

Details

Question Is it right, and is it done?

Axes verification, termination

How it is checked

Checked by the ontology resolution gate, which requires every axis and substrate node that names a layer to resolve

Population Every axis and substrate node that names the layer

Freshness A verdict stands until the layer list or a record that names a layer changes

Refusal The gate fails on an axis or substrate node that names a layer that does not exist

Observation None, because a layer is a grouping of axes, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants an axis that names a missing layer, and the bundled references resolve

Authoritative side The layer list, which every axis and substrate node that names a layer cites

Depends on Not answered

Shape it refuses Not answered

The axes

Each reasoning axis is a typed, terminating question on one layer, listed with the nodes a run may select on it and the contracts positioned on it.

ontology

Details

Question What is it?

Nodes ont-identity, ont-composition, ont-structure, ont-relation, ont-space, ont-time, ont-state, ont-change, ont-behavior, ont-function, ont-cause, ont-meaning, ont-scale, ont-probability, ont-novelty

Contracts Evidence-Before-Generation, Semantic Operation Boundary, Capability Profile, Domain Cache Validation, Scope Extraction, Domain Knowledge Base, DSL Compliance Loading, Workspace Configuration Discovery, Runtime-Neutral Automation Boundary, Capability Degradation, Automation Opportunity Detection, Runtime-Agnostic Adapter Boundary, Capability Disclosure, Iterative Variation Discovery, Detection Registry, Orientation Stage, Authoritative Source Loading, Trust Anchor, Intent & Directionality Normalization, Skeptical Context Acquisition, Dynamic Discovery Pattern Generation, Context Initialization, Trust Anchor Declaration, Coverage Workspace, PAG Document Declaration, Analysis Workspace, Registry Baseline, Profile Compose, Seed Composition, Taxonomy Jurisdiction

How it is checked

Checked by the ontology resolution gate, which requires every node, loop stage and grammar ground that names an axis to resolve

Population Every reasoning node, loop stage and algorithm record that names the axis

Freshness A verdict stands until the axis list or a record that names an axis changes

Refusal The gate fails on a node, stage or ground that names an axis that does not exist

Observation None, because an axis is a category of question, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a node whose axis does not exist and a staged record whose axis is not its stage's axis, and the bundled records validate clean

Authoritative side The axis list, which every node, stage and ground that names an axis cites

Depends on Not answered

Shape it refuses Not answered

analysis

  • Layer: Epistemic
  • Mandatory: when-relevant
  • Math type: graph
  • Selectable: yes

Details

Question How is it to be seen?

Nodes ana-structural, ana-temporal, ana-spatial, ana-statistical, ana-frequency, ana-sequential, ana-relational, ana-behavioral, ana-functional, ana-semantic, ana-causal, ana-predictive, ana-anomaly, ana-evolutionary, ana-fractal

Contracts Non-Destructive Domain Investigation, Risk Complexity Reversibility, Existing Pattern Extraction, Knowledge Documentation Relevance, Breaking Point Calculation, Convention Strength Analysis, Scalability Projection, Research Guidance, Tool Calibration, Lifetime Resolution, Surface Grid Walk, PAG Keyword Ontology, Compliance Gap, Semantic Domain Partitioning, Behavioral Signature Extraction, Cross-Class Pattern Detection, Behavioral Inconsistency, Sequential Chain Duplication, Temporal Coupling Detection, Relational Graph Duplication, Causal Wiring Duplication, Anomaly Outlier Detection, Conceptual Duplication Detection, Fractal Scale Duplication, Path Role Walk

How it is checked

Checked by the ontology resolution gate, which requires every node, loop stage and grammar ground that names an axis to resolve

Population Every reasoning node, loop stage and algorithm record that names the axis

Freshness A verdict stands until the axis list or a record that names an axis changes

Refusal The gate fails on a node, stage or ground that names an axis that does not exist

Observation None, because an axis is a category of question, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a node whose axis does not exist and a staged record whose axis is not its stage's axis, and the bundled records validate clean

Authoritative side The axis list, which every node, stage and ground that names an axis cites

Depends on Not answered

Shape it refuses Not answered

reasoning

  • Layer: Epistemic
  • Mandatory: when-relevant
  • Math type: logic
  • Selectable: yes

Details

Question Why, and what follows?

Nodes rea-observation, rea-description, rea-comparison, rea-classification, rea-explanation, rea-prediction, rea-intervention, rea-creation, rea-reflection

Contracts Principle Extraction, Phase Validation Requirement, Validation Strategy Composition, Hybrid Workflow Orchestration, Context Forking Configuration, Verb-Based Execution Classification, Workflow Type Document Selection, Agent Sequence Definition, Four-Dimensional Agent Graph, Workflow Principles Mapping, Intentional Static Separation, Extension Interface Discovery, Performance-Aware Discovery Design, Dynamic Extension Architecture, Pattern Classification, Refactor Intent Classification, Architecture Compliance Targeting, Existing Solution Conflict, Migration Action Mapping, Atomic Refactor Phase, Planning Stage, Principle Activation, Protocol Semantic Selection, Phase Decomposition, Four-Dimensional Phase Graph, Dependency Linearization, Severity Assignment, Loop Class Labeling, Violation Classification, Invocation Join, Duplicate Disposition Walk, Uncovered Gap Derivation, Technique and Invariant Selection, PAG Node Decomposition, PAG Structure Declaration, PAG Ambiguity Reduction, Anti-Pattern Classification, Abstraction Boundary Principle, Base-Class Candidate Selection, Concrete-vs-Abstract Responsibility Split, Template Method Lifecycle, Migration Ordering, Canonical Config Resolution, Stage Ordering, Concern Classification, Name Projection, Container Ladder, Export Triage Ladder, Dialect Resolution

How it is checked

Checked by the ontology resolution gate, which requires every node, loop stage and grammar ground that names an axis to resolve

Population Every reasoning node, loop stage and algorithm record that names the axis

Freshness A verdict stands until the axis list or a record that names an axis changes

Refusal The gate fails on a node, stage or ground that names an axis that does not exist

Observation None, because an axis is a category of question, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a node whose axis does not exist and a staged record whose axis is not its stage's axis, and the bundled records validate clean

Authoritative side The axis list, which every node, stage and ground that names an axis cites

Depends on Not answered

Shape it refuses Not answered

representation

Details

Question How is it encoded?

Nodes rep-symbolic, rep-numerical, rep-geometric, rep-topological, rep-information-theoretic, rep-probabilistic, rep-dynamical, rep-computational

Contracts Audit Artifact, Final Generation Report, Template Assembly, Automation Session Report, Centralization Report, Rendering Stage, Checklist Output Rendering, Partial Success Reporting, Completion Report, Investigation Report, Action Log, Convergence Walk, Coverage Ledger, Pattern Distillation History, Version Provenance, Living Plan State, Versioned Turn Provenance, Taxonomy Ledger

How it is checked

Checked by the ontology resolution gate, which requires every node, loop stage and grammar ground that names an axis to resolve

Population Every reasoning node, loop stage and algorithm record that names the axis

Freshness A verdict stands until the axis list or a record that names an axis changes

Refusal The gate fails on a node, stage or ground that names an axis that does not exist

Observation None, because an axis is a category of question, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a node whose axis does not exist and a staged record whose axis is not its stage's axis, and the bundled records validate clean

Authoritative side The axis list, which every node, stage and ground that names an axis cites

Depends on Not answered

Shape it refuses Not answered

formalization

Details

Question What does it resolve to?

Nodes for-existence, for-structure, for-relation, for-space, for-transformation, for-invariance, for-uncertainty, for-computation, for-abstraction, for-creation, for-absence

Contracts Portable Contract Composition, Adapter Rendering, Agent Workflow File Modification Recovery, Shared Document Workspace, Agent Document Responsibility, Agent Activation Invocation, Parallel Batch Execution, Sequential Agent Execution, Handoff Signal, Orchestrator Action, Workflow Coordination Sequence, Workflow Recovery Loop, Checklist Integration, Phase Documentation Template, Capability Invocation Protocol, Centralized Reference Resolver, Cache Invalidation Strategy, Manual Fallback Preservation, Dynamic Failure Isolation, Entry Point Migration, Knowledge Capture, Replacement Refactor, Rollback-Centered Execution, Compilation Stage, Codebase Pattern Enforcement, Verb Template Binding, Task Atomization, Ripple Chain Analysis, Validator Coverage, Structured Observability Context, Cross-Cutting Surface Coverage, Legacy Elimination, Hierarchical Numbering, File-Scoped Fix, File Limit Remediation, Import Boundary Remediation, Naming Convention Remediation, Base-Class Compliance Remediation, CSS Token Remediation, DOM Factory Remediation, Console Usage Remediation, Lifecycle Symmetry Remediation, Stylelint Post-Fix, File Modification Recovery, Defensive String Normalization, Safe Arithmetic Contract, Recursion Control, Advanced Tool Escalation, Test Authoring, PAG Explicit Control Flow, PAG Semantic Operation, Base Schematic Composition, Backup-Verified Migration, Registry Regeneration, Anti-Reintroduction Gate, Idempotent Merge, Deterministic Merge Core, Persistence Fork, Comment Normalization Remediation, Custom-Rule Derivation, Composed Turn Contract, Container Reshape

How it is checked

Checked by the ontology resolution gate, which requires every node, loop stage and grammar ground that names an axis to resolve

Population Every reasoning node, loop stage and algorithm record that names the axis

Freshness A verdict stands until the axis list or a record that names an axis changes

Refusal The gate fails on a node, stage or ground that names an axis that does not exist

Observation None, because an axis is a category of question, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a node whose axis does not exist and a staged record whose axis is not its stage's axis, and the bundled records validate clean

Authoritative side The axis list, which every node, stage and ground that names an axis cites

Depends on Not answered

Shape it refuses Not answered

teleology

Details

Question What is it for?

Nodes tel-objective, tel-utility, tel-cost, tel-priority

Contracts Creation History Collision, Adaptive Phase Boundary, Replacement Safety, Static-to-Dynamic Readiness, Automation Operation Mode, Automation Priority Ordering, Operation Mode Gating, Canonical Variation Selection, Developer Decision Gate, Teleological Intent Gate, Admissibility Constraint Gate, Severity-Ordered Remediation, Phase-Separated Execution, Coverage Risk Prioritization, PAG Invariant Record, Anti-Pattern Priority Matrix, Boundary Reconciliation, Reshape Risk Priority, Vocabulary Admission Gate

How it is checked

Checked by the ontology resolution gate, which requires every node, loop stage and grammar ground that names an axis to resolve

Population Every reasoning node, loop stage and algorithm record that names the axis

Freshness A verdict stands until the axis list or a record that names an axis changes

Refusal The gate fails on a node, stage or ground that names an axis that does not exist

Observation None, because an axis is a category of question, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a node whose axis does not exist and a staged record whose axis is not its stage's axis, and the bundled records validate clean

Authoritative side The axis list, which every node, stage and ground that names an axis cites

Depends on Not answered

Shape it refuses Not answered

verification

Details

Question Is it real?

Nodes ver-evidence, ver-ground-truth, ver-falsification, ver-confidence, ver-refutation, ver-population, ver-freshness, ver-standing, ver-refusal, ver-observation

Contracts Semantic Compliance Validation, Evidence Grounding Validation, Algorithmic Embodiment Validation, Workflow Validation Gate, Measured-vs-Estimated Validation, Architecture Validation Before Persistence, Additive Debt Gate, Pattern-Specific Validation, Zero-Duplication Verification, Validation Score, Validation Stage, Semantic Debt Policy, Evidence-Based Claim Verification, Validation Suite Battery, Repair Stage, Bounded Repair Loop, Severity Failure Routing, Verification Loop, Verification Execution, Reverification Gate, Evidence-Gated Claim Verification, Environment Capability Verification, Behavioral Self-Test, Adversarial Input Testing, Recursive Self-Verification, Evidence Verdict, PAG Handoff Gate, Anti-Pattern Elimination Verification, Distillation Metrics, Delta Capture, Plan Phase Verification, Machine Verdict Derivation, Mode Contract Validation, Discovery Verification, Alignment Cadence

How it is checked

Checked by the ontology resolution gate, which requires every node, loop stage and grammar ground that names an axis to resolve

Population Every reasoning node, loop stage and algorithm record that names the axis

Freshness A verdict stands until the axis list or a record that names an axis changes

Refusal The gate fails on a node, stage or ground that names an axis that does not exist

Observation None, because an axis is a category of question, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a node whose axis does not exist and a staged record whose axis is not its stage's axis, and the bundled records validate clean

Authoritative side The axis list, which every node, stage and ground that names an axis cites

Depends on Not answered

Shape it refuses Not answered

termination

Details

Question Is it done?

Nodes ter-completion, ter-saturation, ter-diminishing-returns, ter-block, ter-stop, ter-promotion, ter-publication

Contracts Agent Generation Completion, First-Time Initiation, Automation Completion Status, Completion Truthfulness, Explicit Termination, Early Success Exit, Iteration Bound, Validation Gate, Coverage Completion, PAG Well-Formedness Validation, Pattern Distillation Completion Truthfulness, Phase Close Gate, Bounded Cascade Termination, Taxonomy Completion

How it is checked

Checked by the ontology resolution gate, which requires every node, loop stage and grammar ground that names an axis to resolve

Population Every reasoning node, loop stage and algorithm record that names the axis

Freshness A verdict stands until the axis list or a record that names an axis changes

Refusal The gate fails on a node, stage or ground that names an axis that does not exist

Observation None, because an axis is a category of question, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a node whose axis does not exist and a staged record whose axis is not its stage's axis, and the bundled records validate clean

Authoritative side The axis list, which every node, stage and ground that names an axis cites

Depends on Not answered

Shape it refuses Not answered

The nodes

Every node on the axes is listed with the concept it resolves to, the question it asks, the math type it yields, the shape of its answer, its decision test and its role, and the surfaces and contracts that ground themselves in it.

Identity

Details

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Composition

Details

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Structure

Details

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Relation

Details

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Space

Details

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Time

Details

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

State

Details

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Change

Details

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Behavior

Details

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Function

Details

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Cause

Details

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Meaning

Details

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Scale

Details

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Probability

Details

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Novelty

Details

Grounded by Concrete-vs-Abstract Responsibility Split

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Structural Analysis

Details

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Temporal Analysis

Details

Grounded by Temporal Coupling Detection

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Spatial Analysis

Details

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Statistical Analysis

Details

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Frequency Analysis

Details

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Sequential Analysis

Details

Grounded by Sequential Chain Duplication

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Relational Analysis

Details

Grounded by Relational Graph Duplication

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Behavioral Analysis

Details

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Functional Analysis

Details

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Semantic Analysis

Details

Grounded by Conceptual Duplication Detection

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Causal Analysis

Details

Grounded by Causal Wiring Duplication

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Predictive Analysis

Details

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Anomaly Analysis

Details

Grounded by Anomaly Outlier Detection

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Evolutionary Analysis

Details

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Fractal Analysis

Details

Grounded by Fractal Scale Duplication

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Observation

Details

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Description

Details

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Comparison

Details

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Classification

Details

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Explanation

Details

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Prediction

Details

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Intervention

Details

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Creation

Details

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Reflection

Details

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Symbolic Representation

Details

Question Is it encoded as equations or notation?

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Numerical Representation

Details

Question Is it encoded as quantities?

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Geometric Representation

Details

Question Is it encoded as shapes or coordinates?

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Topological Representation

Details

Question Is it encoded as connectivity or continuity?

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Information-Theoretic Representation

Details

Question Is it encoded as entropy or compression?

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Probabilistic Representation

Details

Question Is it encoded as distributions?

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Dynamical Representation

Details

Question Is it encoded as state transitions?

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Computational Representation

Details

Question Is it encoded as an algorithm?

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Existence

Details

Question What object exists?

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Formal Structure

Details

Question What structure holds?

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Mapping

Details

Question What mapping connects objects?

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Environment

Details

Question What environment contains them?

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Transformation

Details

Question What operation applies?

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Invariance

Details

Question What is preserved?

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Uncertainty

Details

Question What is uncertain?

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Computability

Details

Question What is computable?

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Abstraction

Details

Question What generalizes?

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Emergence

Details

Question What new structure can emerge?

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Absence

Details

Question What is absent, and is it distinguished from unknown, omitted and zero?

Answer shape set

Decision test every absence a later check must distinguish is represented as its own value

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Objective

Details

Question What is the objective?

Grounded by meta_block, meta_field, node_meta_tag

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Branch Utility

Details

Question How much does this advance the objective?

Answer shape number

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Branch Cost

Details

Question What does this cost?

Answer shape number

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Branch Priority

Details

Question Is this the highest-worth admissible branch?

Answer shape boolean

Decision test the branch has the highest utility minus cost among the admissible branches

Role injection-gate

Grounded by Adaptive Phase Boundary, Automation Priority Ordering, Developer Decision Gate, Teleological Intent Gate, Severity Assignment, Severity Failure Routing, Severity-Ordered Remediation, Coverage Risk Prioritization, Anti-Pattern Priority Matrix, Reshape Risk Priority, Vocabulary Admission Gate, priority_queue_declaration

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Evidence

Details

Question What evidence supports this?

Answer shape set

Decision test the evidence set is non-empty

Role both

Grounded by semantic-correctness, functional-correctness, state-correctness, interface-correctness, interaction-correctness, temporal-correctness, concurrency-correctness, memory-correctness, resource-correctness, performance-correctness, reliability-correctness, availability-correctness, consistency-correctness, data-correctness, numerical-correctness, security-correctness, determinism-correctness, protocol-correctness, configuration-correctness, observability-correctness, Evidence Grounding Validation, Workflow Validation Gate, Additive Debt Gate, Zero-Duplication Verification, Evidence-Based Claim Verification, Verification Execution, Reverification Gate, Evidence-Gated Claim Verification, Environment Capability Verification, Recursive Self-Verification, Evidence Verdict, PAG Handoff Gate, Anti-Pattern Elimination Verification, Plan Phase Verification, Machine Verdict Derivation, Mode Contract Validation, Discovery Verification, handoff_gate, check_line, check_marker, report_block

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Ground Truth

Details

Question Is it true against reality, not merely coherent?

Grounded by semantic-correctness, functional-correctness, state-correctness, interface-correctness, interaction-correctness, temporal-correctness, concurrency-correctness, memory-correctness, resource-correctness, performance-correctness, reliability-correctness, availability-correctness, consistency-correctness, data-correctness, numerical-correctness, security-correctness, determinism-correctness, protocol-correctness, configuration-correctness, observability-correctness

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Refutation Condition

Details

Question What would refute it?

Grounded by invariant_record

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Confidence

Details

Question How confident is it, and is that enough?

Answer shape number[0,1]

Decision test confidence is at or above the threshold

Grounded by verdict

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Support Against Refutation

Details

Question Does refutation outweigh support?

Grounded by result_line, repair_edge

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Population

Details

Question Over what set was this checked?

Answer shape ratio

Decision test the declared population is non-empty and every member is measured or named absent

Role both

Grounded by PAG Handoff Gate, population_clause, report_field

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Freshness

Details

Question Was the read derived after the last relevant mutator?

Answer shape boolean

Decision test the fingerprint of the inputs and the code matches the output's declared derivation

Grounded by freshness_clause, report_field

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Standing

Details

Question Did the read set move beneath the verdict?

Answer shape boolean

Decision test the moved set is empty

Grounded by PAG Handoff Gate, standing_line

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Refusal

Details

Question Where does this stage refuse to continue?

Answer shape set

Decision test a refusal condition is named before the irreversible write

Role injection-gate

Grounded by PAG Handoff Gate, refusal_line

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Located Observation

Details

Question Does the observation locate a failure, or is an absence of failures read as proof?

Answer shape set

Decision test every observed location is reported as located, and no observed absence is reported as verified

Grounded by report_field

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Completion

Details

Question Is every task done?

Answer shape boolean

Decision test every task is done

Role completion-marker

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Saturation

Details

Question Is nothing left to resolve?

Answer shape boolean

Decision test no open items remain

Role both

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Diminishing Returns

Details

Question Has progress stopped increasing?

Answer shape counter

Decision test progress is unchanged across a bounded window

Role injection-gate

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Blocked Run

Details

Question Is it blocked on external input?

Answer shape boolean

Grounded by PAG Handoff Gate, result_line, wait_statement

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Stop Condition

Details

Question Do saturation, completion and verification all hold, or is the run blocked?

Answer shape boolean

Decision test saturation, completion and verification all hold, or ter-block holds

Role completion-marker

Grounded by Agent Generation Completion, First-Time Initiation, Automation Completion Status, Completion Truthfulness, Explicit Termination, Iteration Bound, Validation Gate, Coverage Completion, Pattern Distillation Completion Truthfulness, Phase Close Gate, Bounded Cascade Termination, Taxonomy Completion, report_field

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Promotion

Details

Question Is the candidate promoted, or only produced?

Answer shape boolean

Decision test a clean verdict precedes the move into accepted state

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

Publication

Details

Question Is the boundary to the external system explicit, and who crosses it?

Answer shape boolean

Decision test the publication gate names its party

How it is checked

Checked by the structured-document validator, which requires the gate clause each node grounds wherever a document writes, reads, stops or reports

Population Every structured document whose constructs ground the node

Freshness A verdict stands until the document, the grammar or the node changes

Refusal The validator fails a gate that omits the clause the node asks for

Observation None, because a node is a question a gate asks; the answer comes from the check the gate runs

Evidence Watched to fire and to accept: a suite plants a check with no evidence, a gate with no population, a write with no refusal and a node with no gate, and validates a well-formed document clean

Authoritative side The gate clause the node asks for, which every document's gate conforms to

Depends on Not answered

Shape it refuses Not answered

The mathematics

The predicates are typed by these math types, each listed with its contracts and the domains of mathematics it draws on.

set-theory

Details

Question What members exist?

Fields set-theory

Predicate family membership Β· cardinality Β· emptiness

Yields shape set | boolean | ratio

Contracts Evidence-Before-Generation, Capability Profile, Scope Extraction, Domain Knowledge Base, Existing Pattern Extraction, DSL Compliance Loading, Workspace Configuration Discovery, Smell Taxonomy, Responsibility Boundary, Canonical Data, Self-Description Manifest, Runtime Discovery, Canonical Semantics, Self-Description and Discovery, Concept Cluster Extraction, Capability Degradation, Automation Opportunity Detection, Capability Disclosure, Detection Registry, Orientation Stage, Authoritative Source Loading, Skeptical Context Acquisition, Explicit Termination, Context Initialization, Early Success Exit, Trust Anchor Declaration, Duplicate Disposition Walk, Lifetime Resolution, Coverage Workspace, Surface Grid Walk, PAG Document Declaration, PAG Keyword Ontology, Analysis Workspace, Registry Baseline, Semantic Domain Partitioning, Cross-Class Pattern Detection, Temporal Coupling Detection, Profile Compose, Seed Composition, Token Source-of-Truth, Custom Type Registration, Taxonomy Jurisdiction

How it is checked

Checked by the yields check, which holds every algorithm's yields and every node's answer shape within the math type's shapes, the ontology resolution gate over every record that names the math type

Population Every algorithm record, node, axis and substrate node that names the math type

Freshness A verdict stands until the math type's shapes or a record that names it changes

Refusal The gate fails on a yield or answer shape outside the type's shapes, or a reference to a type that does not exist

Observation None, because a math type is a family of answers, and nothing observes it while a run executes

Evidence Watched to fire and to accept: one suite plants a node with a dangling math type, another plants an answer shape outside the type's shapes, and the bundled data validates clean

Authoritative side The math type's shapes, which every yield and answer shape conforms to

Depends on Not answered

Shape it refuses Not answered

logic

Details

Question Does it hold, and what follows from it?

Fields logic

Predicate family boolean predicate

Yields shape boolean

Contracts Semantic Operation Boundary, Domain Cache Validation, Principle Extraction, Phase Validation Requirement, Validation Strategy Composition, Semantic Compliance Validation, Algorithmic Embodiment Validation, Agent Generation Completion, Hybrid Workflow Orchestration, Context Forking Configuration, Verb-Based Execution Classification, Workflow Type Document Selection, Handoff Signal, Orchestrator Action, Workflow Principles Mapping, Workflow Validation Gate, Anti-Pattern Inversion, Architecture Smell Record, Document Truth Alignment, Interface Contract, Substitutability, Extension Point, Behavioral Dispatch, Port Adapter, Transaction Boundary, Idempotent Side Effect, Deterministic Core, Error Boundary, Cache Correctness, Security Policy, Control Plane, Universal Architectural Concern Template, Consumer Config SSOT, Architectural Force Classification, Conflict and Tension Resolution, Violation Detection, Enforcement Gate, Modular Boundary Compliance, Contract Compatibility, Runtime Extensibility, Event and Messaging Consistency, State and Transaction Safety, Correctness Verification, Resilience Policy, Security Governance, Control Plane Coordination, Metaprogramming Safety, Model Lifecycle Governance, Relationship Schema Validation, Constraints Over Shortcuts, Forward Compatibility Over Backward Compatibility, Fail-Fast Over Fallback, Explicit Removal Over Deprecation, Greenfield Over Legacy, Single-Path Determinism Over Dual-Path, Immediacy Over Deferring, Mandatory Over Optional, Now Over For-Now, Observed Execution Over Unobserved, Compression Over Repetition, Approved Evolution Over Unapproved, Enforced Feedback Over Ignored, Single Owner Over Shared Ownership, Bounded Lifetime Over Unbounded, Enforced Symmetry Over Asymmetric Lifecycle, Explicit Retention Over Implicit, Structural Release Over Discipline, Immutable Data Over Mutable State, Errors As Language Over Silent Errors, Explicit Invalidity Over Hidden, Event Emission Over Parent Callbacks, Monotonic Growth Over Retraction, Semantic Addressing Over Location Addressing, Ordinal Time Over Timestamps, Homoiconicity Over Separation, Bounded Complexity Over Unlimited, Computed Health Over Metric Health, Secret Store Over Hardcoded Secrets, Boundary Validation Over Unvalidated Input, Least Privilege Over Broad Privilege, Config Externalization Over Env Fallback, Profile-First Over Unmeasured Optimization, Rule As Code Over Convention, Design By Contract Over Implicit Contract, Versioned Evolution Over Breaking Change, Schema-Validated Boundary Over Untyped, Atomic Boundary Over Partial Commit, Saga Compensation Over Distributed 2PC, Async Events Over Synchronous Cross-Boundary, Observable Signals Over Opaque Runtime, Injected Dependency Over Hidden, Convention Discovery Over Hardcoded Wiring, Declarative Config Over Imperative, Anti-Corruption Layer Over Cross-Context Leak, Injected Nondeterminism Over Hidden, Pattern By Fit Over Speculative Pattern, Runtime-Neutral Automation Boundary, Intentional Static Separation, Extension Interface Discovery, Performance-Aware Discovery Design, Dynamic Extension Architecture, Cache Invalidation Strategy, Dynamic Failure Isolation, Measured-vs-Estimated Validation, Architecture Validation Before Persistence, Automation Completion Status, Runtime-Agnostic Adapter Boundary, Pattern Classification, Refactor Intent Classification, Architecture Compliance Targeting, Existing Solution Conflict, Additive Debt Gate, Pattern-Specific Validation, Zero-Duplication Verification, Completion Truthfulness, Trust Anchor, Intent & Directionality Normalization, Planning Stage, Principle Activation, Protocol Semantic Selection, Loop Class Labeling, Codebase Pattern Enforcement, Validator Coverage, Structured Observability Context, Cross-Cutting Surface Coverage, Legacy Elimination, Validation Stage, Semantic Debt Policy, Evidence-Based Claim Verification, Validation Suite Battery, Verification Execution, Violation Classification, Reverification Gate, Evidence-Gated Claim Verification, Environment Capability Verification, Behavioral Self-Test, Adversarial Input Testing, Safe Arithmetic Contract, Invocation Join, Uncovered Gap Derivation, Evidence Verdict, Coverage Completion, PAG Handoff Gate, PAG Explicit Control Flow, PAG Ambiguity Reduction, PAG Well-Formedness Validation, Anti-Pattern Classification, Abstraction Boundary Principle, Base-Class Candidate Selection, Anti-Pattern Elimination Verification, Pattern Distillation Completion Truthfulness, Delta Capture, Plan Phase Verification, Canonical Config Resolution, Machine Verdict Derivation, Mode Contract Validation, Type-Keyed Appearance, Concern Classification, Discovery Verification, Taxonomy Completion, Container Ladder, Export Triage Ladder, Alignment Cadence

How it is checked

Checked by the yields check, which holds every algorithm's yields and every node's answer shape within the math type's shapes, the ontology resolution gate over every record that names the math type

Population Every algorithm record, node, axis and substrate node that names the math type

Freshness A verdict stands until the math type's shapes or a record that names it changes

Refusal The gate fails on a yield or answer shape outside the type's shapes, or a reference to a type that does not exist

Observation None, because a math type is a family of answers, and nothing observes it while a run executes

Evidence Watched to fire and to accept: one suite plants a node with a dangling math type, another plants an answer shape outside the type's shapes, and the bundled data validates clean

Authoritative side The math type's shapes, which every yield and answer shape conforms to

Depends on Not answered

Shape it refuses Not answered

graph

Details

Question What connects what?

Fields category-theory

Predicate family reachability Β· coverage Β· degree

Yields shape edge-list

Contracts Four-Dimensional Agent Graph, Anti-Pattern Relationship Record, Coupling Control, Observability Trace, Causality Ordering, Finite State Machine, Statecharts, Petri Nets, Architectural Relationship Record, Architecture Knowledge Graph, Dependency Closure, Reinforcement Propagation, Observability and Auditability, Migration Action Mapping, Phase Decomposition, Four-Dimensional Phase Graph, Dependency Linearization, Ripple Chain Analysis, PAG Node Decomposition, PAG Structure Declaration, Relational Graph Duplication, Causal Wiring Duplication, Stage Ordering, Path Role Walk

How it is checked

Checked by the yields check, which holds every algorithm's yields and every node's answer shape within the math type's shapes, the ontology resolution gate over every record that names the math type

Population Every algorithm record, node, axis and substrate node that names the math type

Freshness A verdict stands until the math type's shapes or a record that names it changes

Refusal The gate fails on a yield or answer shape outside the type's shapes, or a reference to a type that does not exist

Observation None, because a math type is a family of answers, and nothing observes it while a run executes

Evidence Watched to fire and to accept: one suite plants a node with a dangling math type, another plants an answer shape outside the type's shapes, and the bundled data validates clean

Authoritative side The math type's shapes, which every yield and answer shape conforms to

Depends on Not answered

Shape it refuses Not answered

algebra

Details

Question How are parts arranged under laws?

Fields algebra

Predicate family composition Β· ordering invariant

Yields shape ordered-structure

Contracts Agent Sequence Definition, Anti-Pattern Remediation Algebra, Structural Mediation, Architecture Refactoring Roadmap, Atomic Refactor Phase, Hierarchical Numbering, Technique and Invariant Selection, Sequential Chain Duplication, Concrete-vs-Abstract Responsibility Split, Template Method Lifecycle, Migration Ordering, Cascade Layer Partition, Assembly Composition, Name Projection, Dialect Resolution

How it is checked

Checked by the yields check, which holds every algorithm's yields and every node's answer shape within the math type's shapes, the ontology resolution gate over every record that names the math type

Population Every algorithm record, node, axis and substrate node that names the math type

Freshness A verdict stands until the math type's shapes or a record that names it changes

Refusal The gate fails on a yield or answer shape outside the type's shapes, or a reference to a type that does not exist

Observation None, because a math type is a family of answers, and nothing observes it while a run executes

Evidence Watched to fire and to accept: one suite plants a node with a dangling math type, another plants an answer shape outside the type's shapes, and the bundled data validates clean

Authoritative side The math type's shapes, which every yield and answer shape conforms to

Depends on Not answered

Shape it refuses Not answered

analysis

Details

Question How do states vary?

Fields analysis

Predicate family operation applied to state

Yields shape operation

Contracts Non-Destructive Domain Investigation, Risk Complexity Reversibility, Event Messaging, Streaming Dataflow, Measurement Normalization, Breaking Point Calculation, Scalability Projection, Behavioral Signature Extraction

How it is checked

Checked by the yields check, which holds every algorithm's yields and every node's answer shape within the math type's shapes, the ontology resolution gate over every record that names the math type

Population Every algorithm record, node, axis and substrate node that names the math type

Freshness A verdict stands until the math type's shapes or a record that names it changes

Refusal The gate fails on a yield or answer shape outside the type's shapes, or a reference to a type that does not exist

Observation None, because a math type is a family of answers, and nothing observes it while a run executes

Evidence Watched to fire and to accept: one suite plants a node with a dangling math type, another plants an answer shape outside the type's shapes, and the bundled data validates clean

Authoritative side The math type's shapes, which every yield and answer shape conforms to

Depends on Not answered

Shape it refuses Not answered

optimization

Details

Question What is admissible or best?

Predicate family validation Β· threshold Β· argmax

Yields shape boolean | ranking | number

Contracts Creation History Collision, Adaptive Phase Boundary, Replacement Safety, First-Time Initiation, Architectural Style Boundary, Verification Fitness, Performance Scaling, Architecture Selection Meta-Algorithm, Severity Policy, Refactor Selection, Architecture Assessment, Pattern Selection, Performance and Scalability, Architecture Evolution Governance, Architectural Recommendation, Architecture Decision Support, Static-to-Dynamic Readiness, Automation Operation Mode, Automation Priority Ordering, Operation Mode Gating, Canonical Variation Selection, Developer Decision Gate, Teleological Intent Gate, Severity Assignment, Admissibility Constraint Gate, Severity Failure Routing, Severity-Ordered Remediation, Phase-Separated Execution, Validation Gate, Coverage Risk Prioritization, PAG Invariant Record, Anti-Pattern Priority Matrix, Boundary Reconciliation, Phase Close Gate, Bounded Cascade Termination, Layer Fitness Enforcement, Reshape Risk Priority, Vocabulary Admission Gate

How it is checked

Checked by the yields check, which holds every algorithm's yields and every node's answer shape within the math type's shapes, the ontology resolution gate over every record that names the math type

Population Every algorithm record, node, axis and substrate node that names the math type

Freshness A verdict stands until the math type's shapes or a record that names it changes

Refusal The gate fails on a yield or answer shape outside the type's shapes, or a reference to a type that does not exist

Observation None, because a math type is a family of answers, and nothing observes it while a run executes

Evidence Watched to fire and to accept: one suite plants a node with a dangling math type, another plants an answer shape outside the type's shapes, and the bundled data validates clean

Authoritative side The math type's shapes, which every yield and answer shape conforms to

Depends on Not answered

Shape it refuses Not answered

topology

Details

Question What is preserved under change?

Fields topology

Predicate family invariant / symmetry

Yields shape boolean

Contracts Domain Boundary, Portability Environment, Fractal Scale Duplication, Placement Isolation

How it is checked

Checked by the yields check, which holds every algorithm's yields and every node's answer shape within the math type's shapes, the ontology resolution gate over every record that names the math type

Population Every algorithm record, node, axis and substrate node that names the math type

Freshness A verdict stands until the math type's shapes or a record that names it changes

Refusal The gate fails on a yield or answer shape outside the type's shapes, or a reference to a type that does not exist

Observation None, because a math type is a family of answers, and nothing observes it while a run executes

Evidence Watched to fire and to accept: one suite plants a node with a dangling math type, another plants an answer shape outside the type's shapes, and the bundled data validates clean

Authoritative side The math type's shapes, which every yield and answer shape conforms to

Depends on Not answered

Shape it refuses Not answered

probability

Details

Question How certain or likely is it?

Fields probability

Predicate family confidence Β· distribution Β· counter

Yields shape number[0,1]

Contracts Knowledge Documentation Relevance, Evidence Grounding Validation, RAG Knowledge Boundary, Queuing Theory, Convention Strength Analysis, Research Guidance, Validation Score, Tool Calibration, Recursive Self-Verification, Compliance Gap, Behavioral Inconsistency, Anomaly Outlier Detection, Distillation Metrics

How it is checked

Checked by the yields check, which holds every algorithm's yields and every node's answer shape within the math type's shapes, the ontology resolution gate over every record that names the math type

Population Every algorithm record, node, axis and substrate node that names the math type

Freshness A verdict stands until the math type's shapes or a record that names it changes

Refusal The gate fails on a yield or answer shape outside the type's shapes, or a reference to a type that does not exist

Observation None, because a math type is a family of answers, and nothing observes it while a run executes

Evidence Watched to fire and to accept: one suite plants a node with a dangling math type, another plants an answer shape outside the type's shapes, and the bundled data validates clean

Authoritative side The math type's shapes, which every yield and answer shape conforms to

Depends on Not answered

Shape it refuses Not answered

information-theory

Details

Question What is novel, and how compressible is it?

Fields information-theory

Predicate family novelty Β· dedup Β· hash

Yields shape hash | novelty-score | boolean

Contracts Audit Artifact, Final Generation Report, Template Assembly, Automation Session Report, Centralization Report, Rendering Stage, Checklist Output Rendering, Partial Success Reporting, Completion Report, Investigation Report, Action Log, Coverage Ledger, Conceptual Duplication Detection, Pattern Distillation History, Version Provenance, Living Plan State, Versioned Turn Provenance, Taxonomy Ledger

How it is checked

Checked by the yields check, which holds every algorithm's yields and every node's answer shape within the math type's shapes, the ontology resolution gate over every record that names the math type

Population Every algorithm record, node, axis and substrate node that names the math type

Freshness A verdict stands until the math type's shapes or a record that names it changes

Refusal The gate fails on a yield or answer shape outside the type's shapes, or a reference to a type that does not exist

Observation None, because a math type is a family of answers, and nothing observes it while a run executes

Evidence Watched to fire and to accept: one suite plants a node with a dangling math type, another plants an answer shape outside the type's shapes, and the bundled data validates clean

Authoritative side The math type's shapes, which every yield and answer shape conforms to

Depends on Not answered

Shape it refuses Not answered

computation

Details

Question What procedure produces it?

Fields computation

Predicate family algorithm / loop

Yields shape procedure

Contracts Portable Contract Composition, Adapter Rendering, Agent Creator Kernel, Agent Workflow File Modification Recovery, Shared Document Workspace, Agent Document Responsibility, Agent Activation Invocation, Parallel Batch Execution, Sequential Agent Execution, Workflow Coordination Sequence, Checklist Integration, Phase Documentation Template, Capability Invocation Protocol, Workflow Creation Kernel, Anti-Pattern Rule Compiler, Architectural Contract Kernel, Construction Boundary, Saga Compensation, Declarative Metaprogramming, Manifest-Driven Documentation, Architecture Fitness Function Generation, Architecture Catalog Compiler, Master Architecture Governance Kernel, Centralized Reference Resolver, Manual Fallback Preservation, Entry Point Migration, Knowledge Capture, Automation Kernel, Replacement Refactor, Rollback-Centered Execution, Centralization Kernel, Dynamic Discovery Pattern Generation, Compilation Stage, Verb Template Binding, Task Atomization, Checklist Creation Kernel, File-Scoped Fix, File Limit Remediation, Import Boundary Remediation, Naming Convention Remediation, Base-Class Compliance Remediation, CSS Token Remediation, DOM Factory Remediation, Console Usage Remediation, Lifecycle Symmetry Remediation, Stylelint Post-Fix, Codebase Verification Kernel, File Modification Recovery, Defensive String Normalization, Advanced Tool Escalation, Contract-Based Verification Kernel, Convergence Walk, Test Authoring, Test Coverage Kernel, PAG Semantic Operation, PAG Authoring Kernel, Base Schematic Composition, Backup-Verified Migration, Registry Regeneration, Anti-Reintroduction Gate, Pattern Distiller Kernel, Idempotent Merge, Deterministic Merge Core, Persistence Fork, Living Profile Kernel, Governed Autonomous Plan Loop, Quality Governance Loop, Comment Normalization Remediation, Custom-Rule Derivation, Composed Turn Contract, Loop-Owned Mode Selection, Governed Construction Boundary, Type-Migration Centralization, Container Reshape, Taxonomy Kernel

How it is checked

Checked by the yields check, which holds every algorithm's yields and every node's answer shape within the math type's shapes, the ontology resolution gate over every record that names the math type

Population Every algorithm record, node, axis and substrate node that names the math type

Freshness A verdict stands until the math type's shapes or a record that names it changes

Refusal The gate fails on a yield or answer shape outside the type's shapes, or a reference to a type that does not exist

Observation None, because a math type is a family of answers, and nothing observes it while a run executes

Evidence Watched to fire and to accept: one suite plants a node with a dangling math type, another plants an answer shape outside the type's shapes, and the bundled data validates clean

Authoritative side The math type's shapes, which every yield and answer shape conforms to

Depends on Not answered

Shape it refuses Not answered

dynamical-systems

Details

Question What stable pattern arises, and has it converged?

Predicate family fixed-point Β· convergence Β· oscillation

Yields shape boolean | counter

Contracts Workflow Recovery Loop, Anti-Pattern Propagation Kernel, Resilience Control, Recovery Deployment, Iterative Variation Discovery, Repair Stage, Bounded Repair Loop, Verification Loop, Iteration Bound, Recursion Control

How it is checked

Checked by the yields check, which holds every algorithm's yields and every node's answer shape within the math type's shapes, the ontology resolution gate over every record that names the math type

Population Every algorithm record, node, axis and substrate node that names the math type

Freshness A verdict stands until the math type's shapes or a record that names it changes

Refusal The gate fails on a yield or answer shape outside the type's shapes, or a reference to a type that does not exist

Observation None, because a math type is a family of answers, and nothing observes it while a run executes

Evidence Watched to fire and to accept: one suite plants a node with a dangling math type, another plants an answer shape outside the type's shapes, and the bundled data validates clean

Authoritative side The math type's shapes, which every yield and answer shape conforms to

Depends on Not answered

Shape it refuses Not answered

number

Details

Studies quantity

Question What can be counted or measured?

How it is checked

Checked by the ontology resolution gate over the math types and foundations that name the domain

Population Every math type and foundation layer that names the domain

Freshness A verdict stands until the domain list or a record that names a domain changes

Refusal The gate fails on a reference to a domain that does not exist

Observation None, because a math domain is a field of study, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a math type that names a missing domain, and the bundled references resolve

Authoritative side The domain list, which every math type and foundation that names a domain cites

Depends on Not answered

Shape it refuses Not answered

algebra

Details

Studies operations and structures

Question What rules govern transformations?

How it is checked

Checked by the ontology resolution gate over the math types and foundations that name the domain

Population Every math type and foundation layer that names the domain

Freshness A verdict stands until the domain list or a record that names a domain changes

Refusal The gate fails on a reference to a domain that does not exist

Observation None, because a math domain is a field of study, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a math type that names a missing domain, and the bundled references resolve

Authoritative side The domain list, which every math type and foundation that names a domain cites

Depends on Not answered

Shape it refuses Not answered

geometry

Details

Studies space and form

Question What shapes and spaces exist?

How it is checked

Checked by the ontology resolution gate over the math types and foundations that name the domain

Population Every math type and foundation layer that names the domain

Freshness A verdict stands until the domain list or a record that names a domain changes

Refusal The gate fails on a reference to a domain that does not exist

Observation None, because a math domain is a field of study, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a math type that names a missing domain, and the bundled references resolve

Authoritative side The domain list, which every math type and foundation that names a domain cites

Depends on Not answered

Shape it refuses Not answered

topology

Details

Studies continuity and connectivity

Question What remains invariant under deformation?

How it is checked

Checked by the ontology resolution gate over the math types and foundations that name the domain

Population Every math type and foundation layer that names the domain

Freshness A verdict stands until the domain list or a record that names a domain changes

Refusal The gate fails on a reference to a domain that does not exist

Observation None, because a math domain is a field of study, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a math type that names a missing domain, and the bundled references resolve

Authoritative side The domain list, which every math type and foundation that names a domain cites

Depends on Not answered

Shape it refuses Not answered

analysis

Details

Studies change and limits

Question How do quantities vary?

How it is checked

Checked by the ontology resolution gate over the math types and foundations that name the domain

Population Every math type and foundation layer that names the domain

Freshness A verdict stands until the domain list or a record that names a domain changes

Refusal The gate fails on a reference to a domain that does not exist

Observation None, because a math domain is a field of study, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a math type that names a missing domain, and the bundled references resolve

Authoritative side The domain list, which every math type and foundation that names a domain cites

Depends on Not answered

Shape it refuses Not answered

logic

Details

Studies truth and inference

Question What statements follow from others?

How it is checked

Checked by the ontology resolution gate over the math types and foundations that name the domain

Population Every math type and foundation layer that names the domain

Freshness A verdict stands until the domain list or a record that names a domain changes

Refusal The gate fails on a reference to a domain that does not exist

Observation None, because a math domain is a field of study, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a math type that names a missing domain, and the bundled references resolve

Authoritative side The domain list, which every math type and foundation that names a domain cites

Depends on Not answered

Shape it refuses Not answered

set-theory

Details

Studies collection and membership

Question What objects can be constructed?

How it is checked

Checked by the ontology resolution gate over the math types and foundations that name the domain

Population Every math type and foundation layer that names the domain

Freshness A verdict stands until the domain list or a record that names a domain changes

Refusal The gate fails on a reference to a domain that does not exist

Observation None, because a math domain is a field of study, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a math type that names a missing domain, and the bundled references resolve

Authoritative side The domain list, which every math type and foundation that names a domain cites

Depends on Not answered

Shape it refuses Not answered

combinatorics

Details

Studies discrete arrangements

Question How many configurations exist?

How it is checked

Checked by the ontology resolution gate over the math types and foundations that name the domain

Population Every math type and foundation layer that names the domain

Freshness A verdict stands until the domain list or a record that names a domain changes

Refusal The gate fails on a reference to a domain that does not exist

Observation None, because a math domain is a field of study, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a math type that names a missing domain, and the bundled references resolve

Authoritative side The domain list, which every math type and foundation that names a domain cites

Depends on Not answered

Shape it refuses Not answered

probability

Details

Studies uncertainty

Question What outcomes are possible and likely?

How it is checked

Checked by the ontology resolution gate over the math types and foundations that name the domain

Population Every math type and foundation layer that names the domain

Freshness A verdict stands until the domain list or a record that names a domain changes

Refusal The gate fails on a reference to a domain that does not exist

Observation None, because a math domain is a field of study, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a math type that names a missing domain, and the bundled references resolve

Authoritative side The domain list, which every math type and foundation that names a domain cites

Depends on Not answered

Shape it refuses Not answered

information-theory

Details

Studies information and compression

Question What patterns can be encoded?

How it is checked

Checked by the ontology resolution gate over the math types and foundations that name the domain

Population Every math type and foundation layer that names the domain

Freshness A verdict stands until the domain list or a record that names a domain changes

Refusal The gate fails on a reference to a domain that does not exist

Observation None, because a math domain is a field of study, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a math type that names a missing domain, and the bundled references resolve

Authoritative side The domain list, which every math type and foundation that names a domain cites

Depends on Not answered

Shape it refuses Not answered

computation

Details

Studies procedures and algorithms

Question What can be generated or solved?

How it is checked

Checked by the ontology resolution gate over the math types and foundations that name the domain

Population Every math type and foundation layer that names the domain

Freshness A verdict stands until the domain list or a record that names a domain changes

Refusal The gate fails on a reference to a domain that does not exist

Observation None, because a math domain is a field of study, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a math type that names a missing domain, and the bundled references resolve

Authoritative side The domain list, which every math type and foundation that names a domain cites

Depends on Not answered

Shape it refuses Not answered

category-theory

Details

Studies relationships between structures

Question How do mathematical worlds connect?

How it is checked

Checked by the ontology resolution gate over the math types and foundations that name the domain

Population Every math type and foundation layer that names the domain

Freshness A verdict stands until the domain list or a record that names a domain changes

Refusal The gate fails on a reference to a domain that does not exist

Observation None, because a math domain is a field of study, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a math type that names a missing domain, and the bundled references resolve

Authoritative side The domain list, which every math type and foundation that names a domain cites

Depends on Not answered

Shape it refuses Not answered

The dimensions

The ontological dimensions are what can be observed about a subject, and each is listed with the test surfaces that observe it.

identity

  • Nature: object

Details

Question What exists?

Surfaces data-correctness

How it is checked

Checked by the test-surface catalog, which pairs each dimension with a lens and the techniques that check the pair, the ontology resolution gate over every surface and node that names the dimension

Population Every test surface and ontology node that names the dimension

Freshness A verdict stands until the dimension, the surfaces that name it or their lenses change

Refusal The gate fails on a surface or node that names a dimension that does not exist

Observation None, because a dimension is a question asked of a system; the techniques its surfaces list observe the system

Evidence Watched to fire and to accept: a suite plants a surface whose dimension does not exist, and the bundled surfaces validate clean

Authoritative side The dimension list, which every surface and node that names a dimension cites

Depends on Not answered

Shape it refuses Not answered

composition

  • Nature: elements

Details

Question What is it made of?

Surfaces memory-correctness, resource-correctness

How it is checked

Checked by the test-surface catalog, which pairs each dimension with a lens and the techniques that check the pair, the ontology resolution gate over every surface and node that names the dimension

Population Every test surface and ontology node that names the dimension

Freshness A verdict stands until the dimension, the surfaces that name it or their lenses change

Refusal The gate fails on a surface or node that names a dimension that does not exist

Observation None, because a dimension is a question asked of a system; the techniques its surfaces list observe the system

Evidence Watched to fire and to accept: a suite plants a surface whose dimension does not exist, and the bundled surfaces validate clean

Authoritative side The dimension list, which every surface and node that names a dimension cites

Depends on Not answered

Shape it refuses Not answered

structure

  • Nature: arrangement

Details

Question How are parts arranged?

Surfaces interface-correctness

How it is checked

Checked by the test-surface catalog, which pairs each dimension with a lens and the techniques that check the pair, the ontology resolution gate over every surface and node that names the dimension

Population Every test surface and ontology node that names the dimension

Freshness A verdict stands until the dimension, the surfaces that name it or their lenses change

Refusal The gate fails on a surface or node that names a dimension that does not exist

Observation None, because a dimension is a question asked of a system; the techniques its surfaces list observe the system

Evidence Watched to fire and to accept: a suite plants a surface whose dimension does not exist, and the bundled surfaces validate clean

Authoritative side The dimension list, which every surface and node that names a dimension cites

Depends on Not answered

Shape it refuses Not answered

relation

  • Nature: mapping

Details

Question What connects it to other things?

Surfaces interaction-correctness, consistency-correctness, protocol-correctness

How it is checked

Checked by the test-surface catalog, which pairs each dimension with a lens and the techniques that check the pair, the ontology resolution gate over every surface and node that names the dimension

Population Every test surface and ontology node that names the dimension

Freshness A verdict stands until the dimension, the surfaces that name it or their lenses change

Refusal The gate fails on a surface or node that names a dimension that does not exist

Observation None, because a dimension is a question asked of a system; the techniques its surfaces list observe the system

Evidence Watched to fire and to accept: a suite plants a surface whose dimension does not exist, and the bundled surfaces validate clean

Authoritative side The dimension list, which every surface and node that names a dimension cites

Depends on Not answered

Shape it refuses Not answered

space

  • Nature: position

Details

Question Where is it?

Fields geometry

How it is checked

Checked by the test-surface catalog, which pairs each dimension with a lens and the techniques that check the pair, the ontology resolution gate over every surface and node that names the dimension

Population Every test surface and ontology node that names the dimension

Freshness A verdict stands until the dimension, the surfaces that name it or their lenses change

Refusal The gate fails on a surface or node that names a dimension that does not exist

Observation None, because a dimension is a question asked of a system; the techniques its surfaces list observe the system

Evidence Watched to fire and to accept: a suite plants a surface whose dimension does not exist, and the bundled surfaces validate clean

Authoritative side The dimension list, which every surface and node that names a dimension cites

Depends on Not answered

Shape it refuses Not answered

time

  • Nature: process

Details

Question When does it occur?

Surfaces temporal-correctness

How it is checked

Checked by the test-surface catalog, which pairs each dimension with a lens and the techniques that check the pair, the ontology resolution gate over every surface and node that names the dimension

Population Every test surface and ontology node that names the dimension

Freshness A verdict stands until the dimension, the surfaces that name it or their lenses change

Refusal The gate fails on a surface or node that names a dimension that does not exist

Observation None, because a dimension is a question asked of a system; the techniques its surfaces list observe the system

Evidence Watched to fire and to accept: a suite plants a surface whose dimension does not exist, and the bundled surfaces validate clean

Authoritative side The dimension list, which every surface and node that names a dimension cites

Depends on Not answered

Shape it refuses Not answered

state

  • Nature: condition

Details

Question What condition is it in?

Surfaces state-correctness, configuration-correctness

How it is checked

Checked by the test-surface catalog, which pairs each dimension with a lens and the techniques that check the pair, the ontology resolution gate over every surface and node that names the dimension

Population Every test surface and ontology node that names the dimension

Freshness A verdict stands until the dimension, the surfaces that name it or their lenses change

Refusal The gate fails on a surface or node that names a dimension that does not exist

Observation None, because a dimension is a question asked of a system; the techniques its surfaces list observe the system

Evidence Watched to fire and to accept: a suite plants a surface whose dimension does not exist, and the bundled surfaces validate clean

Authoritative side The dimension list, which every surface and node that names a dimension cites

Depends on Not answered

Shape it refuses Not answered

change

  • Nature: operation

Details

Question How does it transform?

How it is checked

Checked by the test-surface catalog, which pairs each dimension with a lens and the techniques that check the pair, the ontology resolution gate over every surface and node that names the dimension

Population Every test surface and ontology node that names the dimension

Freshness A verdict stands until the dimension, the surfaces that name it or their lenses change

Refusal The gate fails on a surface or node that names a dimension that does not exist

Observation None, because a dimension is a question asked of a system; the techniques its surfaces list observe the system

Evidence Watched to fire and to accept: a suite plants a surface whose dimension does not exist, and the bundled surfaces validate clean

Authoritative side The dimension list, which every surface and node that names a dimension cites

Depends on Not answered

Shape it refuses Not answered

behavior

  • Nature: dynamics

Details

Question What does it do?

Surfaces concurrency-correctness

How it is checked

Checked by the test-surface catalog, which pairs each dimension with a lens and the techniques that check the pair, the ontology resolution gate over every surface and node that names the dimension

Population Every test surface and ontology node that names the dimension

Freshness A verdict stands until the dimension, the surfaces that name it or their lenses change

Refusal The gate fails on a surface or node that names a dimension that does not exist

Observation None, because a dimension is a question asked of a system; the techniques its surfaces list observe the system

Evidence Watched to fire and to accept: a suite plants a surface whose dimension does not exist, and the bundled surfaces validate clean

Authoritative side The dimension list, which every surface and node that names a dimension cites

Depends on Not answered

Shape it refuses Not answered

function

  • Nature: mapping

Details

Question What role does it fulfill?

Surfaces functional-correctness

How it is checked

Checked by the test-surface catalog, which pairs each dimension with a lens and the techniques that check the pair, the ontology resolution gate over every surface and node that names the dimension

Population Every test surface and ontology node that names the dimension

Freshness A verdict stands until the dimension, the surfaces that name it or their lenses change

Refusal The gate fails on a surface or node that names a dimension that does not exist

Observation None, because a dimension is a question asked of a system; the techniques its surfaces list observe the system

Evidence Watched to fire and to accept: a suite plants a surface whose dimension does not exist, and the bundled surfaces validate clean

Authoritative side The dimension list, which every surface and node that names a dimension cites

Depends on Not answered

Shape it refuses Not answered

cause

  • Nature: mechanism

Details

Question Why does it happen?

Surfaces security-correctness

How it is checked

Checked by the test-surface catalog, which pairs each dimension with a lens and the techniques that check the pair, the ontology resolution gate over every surface and node that names the dimension

Population Every test surface and ontology node that names the dimension

Freshness A verdict stands until the dimension, the surfaces that name it or their lenses change

Refusal The gate fails on a surface or node that names a dimension that does not exist

Observation None, because a dimension is a question asked of a system; the techniques its surfaces list observe the system

Evidence Watched to fire and to accept: a suite plants a surface whose dimension does not exist, and the bundled surfaces validate clean

Authoritative side The dimension list, which every surface and node that names a dimension cites

Depends on Not answered

Shape it refuses Not answered

meaning

  • Nature: semantics

Details

Question What does it signify?

Surfaces semantic-correctness, observability-correctness

How it is checked

Checked by the test-surface catalog, which pairs each dimension with a lens and the techniques that check the pair, the ontology resolution gate over every surface and node that names the dimension

Population Every test surface and ontology node that names the dimension

Freshness A verdict stands until the dimension, the surfaces that name it or their lenses change

Refusal The gate fails on a surface or node that names a dimension that does not exist

Observation None, because a dimension is a question asked of a system; the techniques its surfaces list observe the system

Evidence Watched to fire and to accept: a suite plants a surface whose dimension does not exist, and the bundled surfaces validate clean

Authoritative side The dimension list, which every surface and node that names a dimension cites

Depends on Not answered

Shape it refuses Not answered

scale

  • Nature: hierarchy

Details

Question At what level does it exist?

Surfaces performance-correctness, numerical-correctness

How it is checked

Checked by the test-surface catalog, which pairs each dimension with a lens and the techniques that check the pair, the ontology resolution gate over every surface and node that names the dimension

Population Every test surface and ontology node that names the dimension

Freshness A verdict stands until the dimension, the surfaces that name it or their lenses change

Refusal The gate fails on a surface or node that names a dimension that does not exist

Observation None, because a dimension is a question asked of a system; the techniques its surfaces list observe the system

Evidence Watched to fire and to accept: a suite plants a surface whose dimension does not exist, and the bundled surfaces validate clean

Authoritative side The dimension list, which every surface and node that names a dimension cites

Depends on Not answered

Shape it refuses Not answered

probability

  • Nature: distribution

Details

Question How certain is it?

Surfaces reliability-correctness, availability-correctness

How it is checked

Checked by the test-surface catalog, which pairs each dimension with a lens and the techniques that check the pair, the ontology resolution gate over every surface and node that names the dimension

Population Every test surface and ontology node that names the dimension

Freshness A verdict stands until the dimension, the surfaces that name it or their lenses change

Refusal The gate fails on a surface or node that names a dimension that does not exist

Observation None, because a dimension is a question asked of a system; the techniques its surfaces list observe the system

Evidence Watched to fire and to accept: a suite plants a surface whose dimension does not exist, and the bundled surfaces validate clean

Authoritative side The dimension list, which every surface and node that names a dimension cites

Depends on Not answered

Shape it refuses Not answered

novelty

  • Nature: creation

Details

Question What deviates from expectation?

Surfaces determinism-correctness

How it is checked

Checked by the test-surface catalog, which pairs each dimension with a lens and the techniques that check the pair, the ontology resolution gate over every surface and node that names the dimension

Population Every test surface and ontology node that names the dimension

Freshness A verdict stands until the dimension, the surfaces that name it or their lenses change

Refusal The gate fails on a surface or node that names a dimension that does not exist

Observation None, because a dimension is a question asked of a system; the techniques its surfaces list observe the system

Evidence Watched to fire and to accept: a suite plants a surface whose dimension does not exist, and the bundled surfaces validate clean

Authoritative side The dimension list, which every surface and node that names a dimension cites

Depends on Not answered

Shape it refuses Not answered

The lenses

The analysis lenses are how a subject is seen. Each sits on one universal axis and is listed with the fields of mathematics it draws on, the surfaces and detectors it feeds and the test surfaces that see through it.

structure

Details

Question How are the parts organized?

Fields algebra, category-theory

Surfaces structural_duplication, copy_paste_duplication

Detectors Behavioral Signature Extraction, Cross-Class Pattern Detection

Test surfaces interface-correctness, data-correctness, configuration-correctness

How it is checked

Checked by the detectors each lens names, which resolve to algorithms records and scan code for the lens's duplication shapes, the test-surface catalog, which pairs each lens with a dimension

Population The code the lens's detectors scan, and every surface that names the lens

Freshness A verdict stands until the scanned code, a detector or a surface changes

Refusal The gate fails on a detector that resolves to no record, or a surface that names an unknown lens

Observation None, because a lens is a way of reading structure; its detectors read source, not a running system

Evidence Watched to fire and to accept: one suite plants a surface whose lens does not exist, another plants a detector that resolves to no record, and the bundled data validates clean

Authoritative side The lens list and the algorithm records, which a surface and a detector cite

Depends on Not answered

Shape it refuses Not answered

time

Details

Question How does it vary through time?

Fields differential-equations, dynamical-systems

Surfaces temporal_coupling

Detectors Temporal Coupling Detection

Test surfaces temporal-correctness, concurrency-correctness, availability-correctness

How it is checked

Checked by the detectors each lens names, which resolve to algorithms records and scan code for the lens's duplication shapes, the test-surface catalog, which pairs each lens with a dimension

Population The code the lens's detectors scan, and every surface that names the lens

Freshness A verdict stands until the scanned code, a detector or a surface changes

Refusal The gate fails on a detector that resolves to no record, or a surface that names an unknown lens

Observation None, because a lens is a way of reading structure; its detectors read source, not a running system

Evidence Watched to fire and to accept: one suite plants a surface whose lens does not exist, another plants a detector that resolves to no record, and the bundled data validates clean

Authoritative side The lens list and the algorithm records, which a surface and a detector cite

Depends on Not answered

Shape it refuses Not answered

space

Details

Question How is it distributed in space?

Fields geometry, topology

Surfaces none

Detectors none

How it is checked

Checked by the detectors each lens names, which resolve to algorithms records and scan code for the lens's duplication shapes, the test-surface catalog, which pairs each lens with a dimension

Population The code the lens's detectors scan, and every surface that names the lens

Freshness A verdict stands until the scanned code, a detector or a surface changes

Refusal The gate fails on a detector that resolves to no record, or a surface that names an unknown lens

Observation None, because a lens is a way of reading structure; its detectors read source, not a running system

Evidence Watched to fire and to accept: one suite plants a surface whose lens does not exist, another plants a detector that resolves to no record, and the bundled data validates clean

Authoritative side The lens list and the algorithm records, which a surface and a detector cite

Depends on Not answered

Shape it refuses Not answered

statistical

Details

Question What regularities emerge from many observations?

Fields probability, statistics

Surfaces none

Detectors none

Test surfaces performance-correctness, consistency-correctness

How it is checked

Checked by the detectors each lens names, which resolve to algorithms records and scan code for the lens's duplication shapes, the test-surface catalog, which pairs each lens with a dimension

Population The code the lens's detectors scan, and every surface that names the lens

Freshness A verdict stands until the scanned code, a detector or a surface changes

Refusal The gate fails on a detector that resolves to no record, or a surface that names an unknown lens

Observation None, because a lens is a way of reading structure; its detectors read source, not a running system

Evidence Watched to fire and to accept: one suite plants a surface whose lens does not exist, another plants a detector that resolves to no record, and the bundled data validates clean

Authoritative side The lens list and the algorithm records, which a surface and a detector cite

Depends on Not answered

Shape it refuses Not answered

frequency

  • Nature: recurrence
  • Universal axis: dynamics

Details

Question What repeats, and how often?

Fields harmonic-analysis

Surfaces copy_paste_duplication

Detectors Cross-Class Pattern Detection

Test surfaces observability-correctness

How it is checked

Checked by the detectors each lens names, which resolve to algorithms records and scan code for the lens's duplication shapes, the test-surface catalog, which pairs each lens with a dimension

Population The code the lens's detectors scan, and every surface that names the lens

Freshness A verdict stands until the scanned code, a detector or a surface changes

Refusal The gate fails on a detector that resolves to no record, or a surface that names an unknown lens

Observation None, because a lens is a way of reading structure; its detectors read source, not a running system

Evidence Watched to fire and to accept: one suite plants a surface whose lens does not exist, another plants a detector that resolves to no record, and the bundled data validates clean

Authoritative side The lens list and the algorithm records, which a surface and a detector cite

Depends on Not answered

Shape it refuses Not answered

sequential

  • Nature: order
  • Universal axis: dynamics

Details

Question In what order do things occur?

Fields logic, combinatorics

Surfaces sequential_duplication

Detectors Sequential Chain Duplication

Test surfaces state-correctness, protocol-correctness

How it is checked

Checked by the detectors each lens names, which resolve to algorithms records and scan code for the lens's duplication shapes, the test-surface catalog, which pairs each lens with a dimension

Population The code the lens's detectors scan, and every surface that names the lens

Freshness A verdict stands until the scanned code, a detector or a surface changes

Refusal The gate fails on a detector that resolves to no record, or a surface that names an unknown lens

Observation None, because a lens is a way of reading structure; its detectors read source, not a running system

Evidence Watched to fire and to accept: one suite plants a surface whose lens does not exist, another plants a detector that resolves to no record, and the bundled data validates clean

Authoritative side The lens list and the algorithm records, which a surface and a detector cite

Depends on Not answered

Shape it refuses Not answered

relation

Details

Question What connects what?

Fields algebra, category-theory

Surfaces relational_duplication

Detectors Relational Graph Duplication

Test surfaces interaction-correctness

How it is checked

Checked by the detectors each lens names, which resolve to algorithms records and scan code for the lens's duplication shapes, the test-surface catalog, which pairs each lens with a dimension

Population The code the lens's detectors scan, and every surface that names the lens

Freshness A verdict stands until the scanned code, a detector or a surface changes

Refusal The gate fails on a detector that resolves to no record, or a surface that names an unknown lens

Observation None, because a lens is a way of reading structure; its detectors read source, not a running system

Evidence Watched to fire and to accept: one suite plants a surface whose lens does not exist, another plants a detector that resolves to no record, and the bundled data validates clean

Authoritative side The lens list and the algorithm records, which a surface and a detector cite

Depends on Not answered

Shape it refuses Not answered

behavior

Details

Question How does an entity tend to act?

Fields dynamical-systems

Surfaces behavioral_inconsistency

Detectors Behavioral Inconsistency, Behavioral Signature Extraction

Test surfaces functional-correctness, resource-correctness

How it is checked

Checked by the detectors each lens names, which resolve to algorithms records and scan code for the lens's duplication shapes, the test-surface catalog, which pairs each lens with a dimension

Population The code the lens's detectors scan, and every surface that names the lens

Freshness A verdict stands until the scanned code, a detector or a surface changes

Refusal The gate fails on a detector that resolves to no record, or a surface that names an unknown lens

Observation None, because a lens is a way of reading structure; its detectors read source, not a running system

Evidence Watched to fire and to accept: one suite plants a surface whose lens does not exist, another plants a detector that resolves to no record, and the bundled data validates clean

Authoritative side The lens list and the algorithm records, which a surface and a detector cite

Depends on Not answered

Shape it refuses Not answered

function

Details

Question What role does something perform?

Fields functional-analysis

Surfaces none

Detectors none

How it is checked

Checked by the detectors each lens names, which resolve to algorithms records and scan code for the lens's duplication shapes, the test-surface catalog, which pairs each lens with a dimension

Population The code the lens's detectors scan, and every surface that names the lens

Freshness A verdict stands until the scanned code, a detector or a surface changes

Refusal The gate fails on a detector that resolves to no record, or a surface that names an unknown lens

Observation None, because a lens is a way of reading structure; its detectors read source, not a running system

Evidence Watched to fire and to accept: one suite plants a surface whose lens does not exist, another plants a detector that resolves to no record, and the bundled data validates clean

Authoritative side The lens list and the algorithm records, which a surface and a detector cite

Depends on Not answered

Shape it refuses Not answered

meaning

Details

Question What meaning is conveyed?

Fields none

Surfaces conceptual_duplication

Detectors Conceptual Duplication Detection

Test surfaces semantic-correctness

How it is checked

Checked by the detectors each lens names, which resolve to algorithms records and scan code for the lens's duplication shapes, the test-surface catalog, which pairs each lens with a dimension

Population The code the lens's detectors scan, and every surface that names the lens

Freshness A verdict stands until the scanned code, a detector or a surface changes

Refusal The gate fails on a detector that resolves to no record, or a surface that names an unknown lens

Observation None, because a lens is a way of reading structure; its detectors read source, not a running system

Evidence Watched to fire and to accept: one suite plants a surface whose lens does not exist, another plants a detector that resolves to no record, and the bundled data validates clean

Authoritative side The lens list and the algorithm records, which a surface and a detector cite

Depends on Not answered

Shape it refuses Not answered

cause

Details

Question What produces what?

Fields mathematical-modeling

Surfaces causal_duplication

Detectors Causal Wiring Duplication

Test surfaces security-correctness

How it is checked

Checked by the detectors each lens names, which resolve to algorithms records and scan code for the lens's duplication shapes, the test-surface catalog, which pairs each lens with a dimension

Population The code the lens's detectors scan, and every surface that names the lens

Freshness A verdict stands until the scanned code, a detector or a surface changes

Refusal The gate fails on a detector that resolves to no record, or a surface that names an unknown lens

Observation None, because a lens is a way of reading structure; its detectors read source, not a running system

Evidence Watched to fire and to accept: one suite plants a surface whose lens does not exist, another plants a detector that resolves to no record, and the bundled data validates clean

Authoritative side The lens list and the algorithm records, which a surface and a detector cite

Depends on Not answered

Shape it refuses Not answered

prediction

Details

Question What usually follows?

Fields applied-mathematics

Surfaces none

Detectors none

How it is checked

Checked by the detectors each lens names, which resolve to algorithms records and scan code for the lens's duplication shapes, the test-surface catalog, which pairs each lens with a dimension

Population The code the lens's detectors scan, and every surface that names the lens

Freshness A verdict stands until the scanned code, a detector or a surface changes

Refusal The gate fails on a detector that resolves to no record, or a surface that names an unknown lens

Observation None, because a lens is a way of reading structure; its detectors read source, not a running system

Evidence Watched to fire and to accept: one suite plants a surface whose lens does not exist, another plants a detector that resolves to no record, and the bundled data validates clean

Authoritative side The lens list and the algorithm records, which a surface and a detector cite

Depends on Not answered

Shape it refuses Not answered

anomaly

Details

Question What breaks the normal pattern?

Fields statistics

Surfaces behavioral_inconsistency

Detectors Anomaly Outlier Detection

Test surfaces reliability-correctness, numerical-correctness, determinism-correctness

How it is checked

Checked by the detectors each lens names, which resolve to algorithms records and scan code for the lens's duplication shapes, the test-surface catalog, which pairs each lens with a dimension

Population The code the lens's detectors scan, and every surface that names the lens

Freshness A verdict stands until the scanned code, a detector or a surface changes

Refusal The gate fails on a detector that resolves to no record, or a surface that names an unknown lens

Observation None, because a lens is a way of reading structure; its detectors read source, not a running system

Evidence Watched to fire and to accept: one suite plants a surface whose lens does not exist, another plants a detector that resolves to no record, and the bundled data validates clean

Authoritative side The lens list and the algorithm records, which a surface and a detector cite

Depends on Not answered

Shape it refuses Not answered

change

  • Nature: development
  • Universal axis: dynamics

Details

Question How does the pattern itself change?

Fields dynamical-systems

Surfaces none

Detectors none

Test surfaces memory-correctness

How it is checked

Checked by the detectors each lens names, which resolve to algorithms records and scan code for the lens's duplication shapes, the test-surface catalog, which pairs each lens with a dimension

Population The code the lens's detectors scan, and every surface that names the lens

Freshness A verdict stands until the scanned code, a detector or a surface changes

Refusal The gate fails on a detector that resolves to no record, or a surface that names an unknown lens

Observation None, because a lens is a way of reading structure; its detectors read source, not a running system

Evidence Watched to fire and to accept: one suite plants a surface whose lens does not exist, another plants a detector that resolves to no record, and the bundled data validates clean

Authoritative side The lens list and the algorithm records, which a surface and a detector cite

Depends on Not answered

Shape it refuses Not answered

fractal

Details

Question Does the same structure recur at different scales?

Fields fractal-geometry, renormalization

Surfaces scale_duplication

Detectors Fractal Scale Duplication

How it is checked

Checked by the detectors each lens names, which resolve to algorithms records and scan code for the lens's duplication shapes, the test-surface catalog, which pairs each lens with a dimension

Population The code the lens's detectors scan, and every surface that names the lens

Freshness A verdict stands until the scanned code, a detector or a surface changes

Refusal The gate fails on a detector that resolves to no record, or a surface that names an unknown lens

Observation None, because a lens is a way of reading structure; its detectors read source, not a running system

Evidence Watched to fire and to accept: one suite plants a surface whose lens does not exist, another plants a detector that resolves to no record, and the bundled data validates clean

Authoritative side The lens list and the algorithm records, which a surface and a detector cite

Depends on Not answered

Shape it refuses Not answered

transformation

  • Nature: transformation
  • Universal axis: dynamics

Details

Question How does one state become another?

Fields algebra, computation

Surfaces none

Detectors none

How it is checked

Checked by the detectors each lens names, which resolve to algorithms records and scan code for the lens's duplication shapes, the test-surface catalog, which pairs each lens with a dimension

Population The code the lens's detectors scan, and every surface that names the lens

Freshness A verdict stands until the scanned code, a detector or a surface changes

Refusal The gate fails on a detector that resolves to no record, or a surface that names an unknown lens

Observation None, because a lens is a way of reading structure; its detectors read source, not a running system

Evidence Watched to fire and to accept: one suite plants a surface whose lens does not exist, another plants a detector that resolves to no record, and the bundled data validates clean

Authoritative side The lens list and the algorithm records, which a surface and a detector cite

Depends on Not answered

Shape it refuses Not answered

invariant

Details

Question What remains unchanged?

Fields topology, symmetry

Surfaces none

Detectors none

How it is checked

Checked by the detectors each lens names, which resolve to algorithms records and scan code for the lens's duplication shapes, the test-surface catalog, which pairs each lens with a dimension

Population The code the lens's detectors scan, and every surface that names the lens

Freshness A verdict stands until the scanned code, a detector or a surface changes

Refusal The gate fails on a detector that resolves to no record, or a surface that names an unknown lens

Observation None, because a lens is a way of reading structure; its detectors read source, not a running system

Evidence Watched to fire and to accept: one suite plants a surface whose lens does not exist, another plants a detector that resolves to no record, and the bundled data validates clean

Authoritative side The lens list and the algorithm records, which a surface and a detector cite

Depends on Not answered

Shape it refuses Not answered

optimization

Details

Question What is the best possible state?

Fields operations-research

Surfaces none

Detectors none

How it is checked

Checked by the detectors each lens names, which resolve to algorithms records and scan code for the lens's duplication shapes, the test-surface catalog, which pairs each lens with a dimension

Population The code the lens's detectors scan, and every surface that names the lens

Freshness A verdict stands until the scanned code, a detector or a surface changes

Refusal The gate fails on a detector that resolves to no record, or a surface that names an unknown lens

Observation None, because a lens is a way of reading structure; its detectors read source, not a running system

Evidence Watched to fire and to accept: one suite plants a surface whose lens does not exist, another plants a detector that resolves to no record, and the bundled data validates clean

Authoritative side The lens list and the algorithm records, which a surface and a detector cite

Depends on Not answered

Shape it refuses Not answered

complexity

Details

Question How difficult is the transformation?

Fields computation-theory

Surfaces none

Detectors none

How it is checked

Checked by the detectors each lens names, which resolve to algorithms records and scan code for the lens's duplication shapes, the test-surface catalog, which pairs each lens with a dimension

Population The code the lens's detectors scan, and every surface that names the lens

Freshness A verdict stands until the scanned code, a detector or a surface changes

Refusal The gate fails on a detector that resolves to no record, or a surface that names an unknown lens

Observation None, because a lens is a way of reading structure; its detectors read source, not a running system

Evidence Watched to fire and to accept: one suite plants a surface whose lens does not exist, another plants a detector that resolves to no record, and the bundled data validates clean

Authoritative side The lens list and the algorithm records, which a surface and a detector cite

Depends on Not answered

Shape it refuses Not answered

The modes

Each reasoning mode is listed with the practice it names and the techniques that work in it.

observation

Details

Mode identifying patterns or examples

Question What is there?

Techniques static-analysis, runtime-validation, profiling, heap-analysis, monitoring

How it is checked

Checked by the ontology resolution gate over the techniques, nodes and structured-document constructs that name the mode, the model-step check for every model whose steps are modes

Population Every technique, node, model step and document construct that names the mode

Freshness A verdict stands until the mode list or a record that names a mode changes

Refusal The gate fails on a technique, node, model step or construct that names a mode that does not exist

Observation None, because a mode is a way of reasoning, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a technique whose mode does not exist, and the bundled records validate clean

Authoritative side The mode list, which every technique, node, step and construct that names a mode cites

Depends on Not answered

Shape it refuses Not answered

description

Details

Mode defining objects

Question How can it be characterized?

Techniques tracing

How it is checked

Checked by the ontology resolution gate over the techniques, nodes and structured-document constructs that name the mode, the model-step check for every model whose steps are modes

Population Every technique, node, model step and document construct that names the mode

Freshness A verdict stands until the mode list or a record that names a mode changes

Refusal The gate fails on a technique, node, model step or construct that names a mode that does not exist

Observation None, because a mode is a way of reasoning, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a technique whose mode does not exist, and the bundled records validate clean

Authoritative side The mode list, which every technique, node, step and construct that names a mode cites

Depends on Not answered

Shape it refuses Not answered

comparison

Details

Mode finding similarities and differences

Question How is it similar or different?

Techniques unit-testing, integration-testing, end-to-end-testing, differential-testing, contract-testing, assertion-checking, read-after-write-verification

How it is checked

Checked by the ontology resolution gate over the techniques, nodes and structured-document constructs that name the mode, the model-step check for every model whose steps are modes

Population Every technique, node, model step and document construct that names the mode

Freshness A verdict stands until the mode list or a record that names a mode changes

Refusal The gate fails on a technique, node, model step or construct that names a mode that does not exist

Observation None, because a mode is a way of reasoning, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a technique whose mode does not exist, and the bundled records validate clean

Authoritative side The mode list, which every technique, node, step and construct that names a mode cites

Depends on Not answered

Shape it refuses Not answered

classification

Details

Mode grouping by properties

Question Which kind is it?

Techniques property-based-testing

How it is checked

Checked by the ontology resolution gate over the techniques, nodes and structured-document constructs that name the mode, the model-step check for every model whose steps are modes

Population Every technique, node, model step and document construct that names the mode

Freshness A verdict stands until the mode list or a record that names a mode changes

Refusal The gate fails on a technique, node, model step or construct that names a mode that does not exist

Observation None, because a mode is a way of reasoning, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a technique whose mode does not exist, and the bundled records validate clean

Authoritative side The mode list, which every technique, node, step and construct that names a mode cites

Depends on Not answered

Shape it refuses Not answered

abstraction

Details

Mode removing irrelevant details

How it is checked

Checked by the ontology resolution gate over the techniques, nodes and structured-document constructs that name the mode, the model-step check for every model whose steps are modes

Population Every technique, node, model step and document construct that names the mode

Freshness A verdict stands until the mode list or a record that names a mode changes

Refusal The gate fails on a technique, node, model step or construct that names a mode that does not exist

Observation None, because a mode is a way of reasoning, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a technique whose mode does not exist, and the bundled records validate clean

Authoritative side The mode list, which every technique, node, step and construct that names a mode cites

Depends on Not answered

Shape it refuses Not answered

generalization

Details

Mode extending examples into principles

How it is checked

Checked by the ontology resolution gate over the techniques, nodes and structured-document constructs that name the mode, the model-step check for every model whose steps are modes

Population Every technique, node, model step and document construct that names the mode

Freshness A verdict stands until the mode list or a record that names a mode changes

Refusal The gate fails on a technique, node, model step or construct that names a mode that does not exist

Observation None, because a mode is a way of reasoning, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a technique whose mode does not exist, and the bundled records validate clean

Authoritative side The mode list, which every technique, node, step and construct that names a mode cites

Depends on Not answered

Shape it refuses Not answered

formalization

Details

Mode expressing ideas symbolically

How it is checked

Checked by the ontology resolution gate over the techniques, nodes and structured-document constructs that name the mode, the model-step check for every model whose steps are modes

Population Every technique, node, model step and document construct that names the mode

Freshness A verdict stands until the mode list or a record that names a mode changes

Refusal The gate fails on a technique, node, model step or construct that names a mode that does not exist

Observation None, because a mode is a way of reasoning, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a technique whose mode does not exist, and the bundled records validate clean

Authoritative side The mode list, which every technique, node, step and construct that names a mode cites

Depends on Not answered

Shape it refuses Not answered

explanation

Details

Mode identifying mechanisms

Question Why is it this way?

Techniques model-checking

How it is checked

Checked by the ontology resolution gate over the techniques, nodes and structured-document constructs that name the mode, the model-step check for every model whose steps are modes

Population Every technique, node, model step and document construct that names the mode

Freshness A verdict stands until the mode list or a record that names a mode changes

Refusal The gate fails on a technique, node, model step or construct that names a mode that does not exist

Observation None, because a mode is a way of reasoning, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a technique whose mode does not exist, and the bundled records validate clean

Authoritative side The mode list, which every technique, node, step and construct that names a mode cites

Depends on Not answered

Shape it refuses Not answered

deduction

Details

Mode deriving necessary consequences

How it is checked

Checked by the ontology resolution gate over the techniques, nodes and structured-document constructs that name the mode, the model-step check for every model whose steps are modes

Population Every technique, node, model step and document construct that names the mode

Freshness A verdict stands until the mode list or a record that names a mode changes

Refusal The gate fails on a technique, node, model step or construct that names a mode that does not exist

Observation None, because a mode is a way of reasoning, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a technique whose mode does not exist, and the bundled records validate clean

Authoritative side The mode list, which every technique, node, step and construct that names a mode cites

Depends on Not answered

Shape it refuses Not answered

construction

Details

Mode building objects that satisfy rules

How it is checked

Checked by the ontology resolution gate over the techniques, nodes and structured-document constructs that name the mode, the model-step check for every model whose steps are modes

Population Every technique, node, model step and document construct that names the mode

Freshness A verdict stands until the mode list or a record that names a mode changes

Refusal The gate fails on a technique, node, model step or construct that names a mode that does not exist

Observation None, because a mode is a way of reasoning, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a technique whose mode does not exist, and the bundled records validate clean

Authoritative side The mode list, which every technique, node, step and construct that names a mode cites

Depends on Not answered

Shape it refuses Not answered

proof

Details

Mode establishing certainty

How it is checked

Checked by the ontology resolution gate over the techniques, nodes and structured-document constructs that name the mode, the model-step check for every model whose steps are modes

Population Every technique, node, model step and document construct that names the mode

Freshness A verdict stands until the mode list or a record that names a mode changes

Refusal The gate fails on a technique, node, model step or construct that names a mode that does not exist

Observation None, because a mode is a way of reasoning, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a technique whose mode does not exist, and the bundled records validate clean

Authoritative side The mode list, which every technique, node, step and construct that names a mode cites

Depends on Not answered

Shape it refuses Not answered

prediction

Details

Mode inferring future states

Question What comes next?

Techniques load-testing, stress-testing

How it is checked

Checked by the ontology resolution gate over the techniques, nodes and structured-document constructs that name the mode, the model-step check for every model whose steps are modes

Population Every technique, node, model step and document construct that names the mode

Freshness A verdict stands until the mode list or a record that names a mode changes

Refusal The gate fails on a technique, node, model step or construct that names a mode that does not exist

Observation None, because a mode is a way of reasoning, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a technique whose mode does not exist, and the bundled records validate clean

Authoritative side The mode list, which every technique, node, step and construct that names a mode cites

Depends on Not answered

Shape it refuses Not answered

optimization

Details

Mode selecting preferred solutions

How it is checked

Checked by the ontology resolution gate over the techniques, nodes and structured-document constructs that name the mode, the model-step check for every model whose steps are modes

Population Every technique, node, model step and document construct that names the mode

Freshness A verdict stands until the mode list or a record that names a mode changes

Refusal The gate fails on a technique, node, model step or construct that names a mode that does not exist

Observation None, because a mode is a way of reasoning, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a technique whose mode does not exist, and the bundled records validate clean

Authoritative side The mode list, which every technique, node, step and construct that names a mode cites

Depends on Not answered

Shape it refuses Not answered

intervention

Details

Mode modifying systems

Question How can it be changed?

Techniques fault-injection, chaos-testing, mutation-testing

How it is checked

Checked by the ontology resolution gate over the techniques, nodes and structured-document constructs that name the mode, the model-step check for every model whose steps are modes

Population Every technique, node, model step and document construct that names the mode

Freshness A verdict stands until the mode list or a record that names a mode changes

Refusal The gate fails on a technique, node, model step or construct that names a mode that does not exist

Observation None, because a mode is a way of reasoning, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a technique whose mode does not exist, and the bundled records validate clean

Authoritative side The mode list, which every technique, node, step and construct that names a mode cites

Depends on Not answered

Shape it refuses Not answered

creation

Details

Mode generating new structures

Question Can new examples be produced?

Techniques fuzz-testing

How it is checked

Checked by the ontology resolution gate over the techniques, nodes and structured-document constructs that name the mode, the model-step check for every model whose steps are modes

Population Every technique, node, model step and document construct that names the mode

Freshness A verdict stands until the mode list or a record that names a mode changes

Refusal The gate fails on a technique, node, model step or construct that names a mode that does not exist

Observation None, because a mode is a way of reasoning, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a technique whose mode does not exist, and the bundled records validate clean

Authoritative side The mode list, which every technique, node, step and construct that names a mode cites

Depends on Not answered

Shape it refuses Not answered

reflection

Details

Mode discovering the principles behind the examples

Question What general principles emerge?

Techniques deterministic-replay

How it is checked

Checked by the ontology resolution gate over the techniques, nodes and structured-document constructs that name the mode, the model-step check for every model whose steps are modes

Population Every technique, node, model step and document construct that names the mode

Freshness A verdict stands until the mode list or a record that names a mode changes

Refusal The gate fails on a technique, node, model step or construct that names a mode that does not exist

Observation None, because a mode is a way of reasoning, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a technique whose mode does not exist, and the bundled records validate clean

Authoritative side The mode list, which every technique, node, step and construct that names a mode cites

Depends on Not answered

Shape it refuses Not answered

The representations

A result can be encoded in any of these representation layers.

symbolic

Details

equations, formulas, notation

How it is checked

Checked by the ontology resolution gate over the nodes and structured-document constructs that name the representation

Population Every node and document construct that names the representation

Freshness A verdict stands until the representations or a record that names one changes

Refusal The gate fails on a node or construct that names a representation that does not exist

Observation None, because a representation is a form of encoding, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a node that names a missing representation, and the bundled references resolve

Authoritative side The representation list, which every node and construct that names a representation cites

Depends on Not answered

Shape it refuses Not answered

logical

Details

statements, predicates, proofs

How it is checked

Checked by the ontology resolution gate over the nodes and structured-document constructs that name the representation

Population Every node and document construct that names the representation

Freshness A verdict stands until the representations or a record that names one changes

Refusal The gate fails on a node or construct that names a representation that does not exist

Observation None, because a representation is a form of encoding, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a node that names a missing representation, and the bundled references resolve

Authoritative side The representation list, which every node and construct that names a representation cites

Depends on Not answered

Shape it refuses Not answered

numerical

Details

numbers, quantities, measurements

How it is checked

Checked by the ontology resolution gate over the nodes and structured-document constructs that name the representation

Population Every node and document construct that names the representation

Freshness A verdict stands until the representations or a record that names one changes

Refusal The gate fails on a node or construct that names a representation that does not exist

Observation None, because a representation is a form of encoding, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a node that names a missing representation, and the bundled references resolve

Authoritative side The representation list, which every node and construct that names a representation cites

Depends on Not answered

Shape it refuses Not answered

algebraic

Details

operations, groups, fields

How it is checked

Checked by the ontology resolution gate over the nodes and structured-document constructs that name the representation

Population Every node and document construct that names the representation

Freshness A verdict stands until the representations or a record that names one changes

Refusal The gate fails on a node or construct that names a representation that does not exist

Observation None, because a representation is a form of encoding, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a node that names a missing representation, and the bundled references resolve

Authoritative side The representation list, which every node and construct that names a representation cites

Depends on Not answered

Shape it refuses Not answered

geometric

Details

shapes, coordinates, spaces

How it is checked

Checked by the ontology resolution gate over the nodes and structured-document constructs that name the representation

Population Every node and document construct that names the representation

Freshness A verdict stands until the representations or a record that names one changes

Refusal The gate fails on a node or construct that names a representation that does not exist

Observation None, because a representation is a form of encoding, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a node that names a missing representation, and the bundled references resolve

Authoritative side The representation list, which every node and construct that names a representation cites

Depends on Not answered

Shape it refuses Not answered

topological

Details

connectivity, continuity

How it is checked

Checked by the ontology resolution gate over the nodes and structured-document constructs that name the representation

Population Every node and document construct that names the representation

Freshness A verdict stands until the representations or a record that names one changes

Refusal The gate fails on a node or construct that names a representation that does not exist

Observation None, because a representation is a form of encoding, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a node that names a missing representation, and the bundled references resolve

Authoritative side The representation list, which every node and construct that names a representation cites

Depends on Not answered

Shape it refuses Not answered

graphical

Details

diagrams, graphs, networks

How it is checked

Checked by the ontology resolution gate over the nodes and structured-document constructs that name the representation

Population Every node and document construct that names the representation

Freshness A verdict stands until the representations or a record that names one changes

Refusal The gate fails on a node or construct that names a representation that does not exist

Observation None, because a representation is a form of encoding, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a node that names a missing representation, and the bundled references resolve

Authoritative side The representation list, which every node and construct that names a representation cites

Depends on Not answered

Shape it refuses Not answered

matrix

Details

linear transformations

How it is checked

Checked by the ontology resolution gate over the nodes and structured-document constructs that name the representation

Population Every node and document construct that names the representation

Freshness A verdict stands until the representations or a record that names one changes

Refusal The gate fails on a node or construct that names a representation that does not exist

Observation None, because a representation is a form of encoding, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a node that names a missing representation, and the bundled references resolve

Authoritative side The representation list, which every node and construct that names a representation cites

Depends on Not answered

Shape it refuses Not answered

functional

Details

mappings between spaces

How it is checked

Checked by the ontology resolution gate over the nodes and structured-document constructs that name the representation

Population Every node and document construct that names the representation

Freshness A verdict stands until the representations or a record that names one changes

Refusal The gate fails on a node or construct that names a representation that does not exist

Observation None, because a representation is a form of encoding, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a node that names a missing representation, and the bundled references resolve

Authoritative side The representation list, which every node and construct that names a representation cites

Depends on Not answered

Shape it refuses Not answered

information-theoretic

Details

entropy, encoding, compression

How it is checked

Checked by the ontology resolution gate over the nodes and structured-document constructs that name the representation

Population Every node and document construct that names the representation

Freshness A verdict stands until the representations or a record that names one changes

Refusal The gate fails on a node or construct that names a representation that does not exist

Observation None, because a representation is a form of encoding, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a node that names a missing representation, and the bundled references resolve

Authoritative side The representation list, which every node and construct that names a representation cites

Depends on Not answered

Shape it refuses Not answered

probabilistic

Details

distributions and likelihoods

How it is checked

Checked by the ontology resolution gate over the nodes and structured-document constructs that name the representation

Population Every node and document construct that names the representation

Freshness A verdict stands until the representations or a record that names one changes

Refusal The gate fails on a node or construct that names a representation that does not exist

Observation None, because a representation is a form of encoding, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a node that names a missing representation, and the bundled references resolve

Authoritative side The representation list, which every node and construct that names a representation cites

Depends on Not answered

Shape it refuses Not answered

dynamical

Details

state transitions

How it is checked

Checked by the ontology resolution gate over the nodes and structured-document constructs that name the representation

Population Every node and document construct that names the representation

Freshness A verdict stands until the representations or a record that names one changes

Refusal The gate fails on a node or construct that names a representation that does not exist

Observation None, because a representation is a form of encoding, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a node that names a missing representation, and the bundled references resolve

Authoritative side The representation list, which every node and construct that names a representation cites

Depends on Not answered

Shape it refuses Not answered

computational

Details

algorithms and programs

How it is checked

Checked by the ontology resolution gate over the nodes and structured-document constructs that name the representation

Population Every node and document construct that names the representation

Freshness A verdict stands until the representations or a record that names one changes

Refusal The gate fails on a node or construct that names a representation that does not exist

Observation None, because a representation is a form of encoding, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a node that names a missing representation, and the bundled references resolve

Authoritative side The representation list, which every node and construct that names a representation cites

Depends on Not answered

Shape it refuses Not answered

categorical

Details

objects and morphisms

How it is checked

Checked by the ontology resolution gate over the nodes and structured-document constructs that name the representation

Population Every node and document construct that names the representation

Freshness A verdict stands until the representations or a record that names one changes

Refusal The gate fails on a node or construct that names a representation that does not exist

Observation None, because a representation is a form of encoding, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a node that names a missing representation, and the bundled references resolve

Authoritative side The representation list, which every node and construct that names a representation cites

Depends on Not answered

Shape it refuses Not answered

The pattern types

Each pattern type is listed with the mathematical viewpoint it takes.

symbolic

Details

formal systems and equations

How it is checked

Checked by the ontology resolution gate over every ground that names the pattern type

Population Every construct and record that grounds the pattern type

Freshness A verdict stands until the pattern types or a record that names one changes

Refusal The gate fails on a ground that names a pattern type that does not exist

Observation None, because a pattern type is a viewpoint on structure, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a ground whose kind exists and whose id does not, and a ground filed under the wrong kind, and passes a well-formed one

Authoritative side The pattern type list, which every ground that names a type cites

Depends on Not answered

Shape it refuses Not answered

numerical

Details

quantity and arithmetic

How it is checked

Checked by the ontology resolution gate over every ground that names the pattern type

Population Every construct and record that grounds the pattern type

Freshness A verdict stands until the pattern types or a record that names one changes

Refusal The gate fails on a ground that names a pattern type that does not exist

Observation None, because a pattern type is a viewpoint on structure, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a ground whose kind exists and whose id does not, and a ground filed under the wrong kind, and passes a well-formed one

Authoritative side The pattern type list, which every ground that names a type cites

Depends on Not answered

Shape it refuses Not answered

algebraic

Details

operations and transformations

How it is checked

Checked by the ontology resolution gate over every ground that names the pattern type

Population Every construct and record that grounds the pattern type

Freshness A verdict stands until the pattern types or a record that names one changes

Refusal The gate fails on a ground that names a pattern type that does not exist

Observation None, because a pattern type is a viewpoint on structure, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a ground whose kind exists and whose id does not, and a ground filed under the wrong kind, and passes a well-formed one

Authoritative side The pattern type list, which every ground that names a type cites

Depends on Not answered

Shape it refuses Not answered

geometric

Details

shape and space

How it is checked

Checked by the ontology resolution gate over every ground that names the pattern type

Population Every construct and record that grounds the pattern type

Freshness A verdict stands until the pattern types or a record that names one changes

Refusal The gate fails on a ground that names a pattern type that does not exist

Observation None, because a pattern type is a viewpoint on structure, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a ground whose kind exists and whose id does not, and a ground filed under the wrong kind, and passes a well-formed one

Authoritative side The pattern type list, which every ground that names a type cites

Depends on Not answered

Shape it refuses Not answered

topological

Details

connectivity and invariance

How it is checked

Checked by the ontology resolution gate over every ground that names the pattern type

Population Every construct and record that grounds the pattern type

Freshness A verdict stands until the pattern types or a record that names one changes

Refusal The gate fails on a ground that names a pattern type that does not exist

Observation None, because a pattern type is a viewpoint on structure, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a ground whose kind exists and whose id does not, and a ground filed under the wrong kind, and passes a well-formed one

Authoritative side The pattern type list, which every ground that names a type cites

Depends on Not answered

Shape it refuses Not answered

logical

Details

truth and implication

How it is checked

Checked by the ontology resolution gate over every ground that names the pattern type

Population Every construct and record that grounds the pattern type

Freshness A verdict stands until the pattern types or a record that names one changes

Refusal The gate fails on a ground that names a pattern type that does not exist

Observation None, because a pattern type is a viewpoint on structure, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a ground whose kind exists and whose id does not, and a ground filed under the wrong kind, and passes a well-formed one

Authoritative side The pattern type list, which every ground that names a type cites

Depends on Not answered

Shape it refuses Not answered

combinatorial

Details

possible arrangements

How it is checked

Checked by the ontology resolution gate over every ground that names the pattern type

Population Every construct and record that grounds the pattern type

Freshness A verdict stands until the pattern types or a record that names one changes

Refusal The gate fails on a ground that names a pattern type that does not exist

Observation None, because a pattern type is a viewpoint on structure, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a ground whose kind exists and whose id does not, and a ground filed under the wrong kind, and passes a well-formed one

Authoritative side The pattern type list, which every ground that names a type cites

Depends on Not answered

Shape it refuses Not answered

statistical

Details

distribution and variation

How it is checked

Checked by the ontology resolution gate over every ground that names the pattern type

Population Every construct and record that grounds the pattern type

Freshness A verdict stands until the pattern types or a record that names one changes

Refusal The gate fails on a ground that names a pattern type that does not exist

Observation None, because a pattern type is a viewpoint on structure, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a ground whose kind exists and whose id does not, and a ground filed under the wrong kind, and passes a well-formed one

Authoritative side The pattern type list, which every ground that names a type cites

Depends on Not answered

Shape it refuses Not answered

probabilistic

Details

randomness and uncertainty

How it is checked

Checked by the ontology resolution gate over every ground that names the pattern type

Population Every construct and record that grounds the pattern type

Freshness A verdict stands until the pattern types or a record that names one changes

Refusal The gate fails on a ground that names a pattern type that does not exist

Observation None, because a pattern type is a viewpoint on structure, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a ground whose kind exists and whose id does not, and a ground filed under the wrong kind, and passes a well-formed one

Authoritative side The pattern type list, which every ground that names a type cites

Depends on Not answered

Shape it refuses Not answered

information

Details

compression and complexity

How it is checked

Checked by the ontology resolution gate over every ground that names the pattern type

Population Every construct and record that grounds the pattern type

Freshness A verdict stands until the pattern types or a record that names one changes

Refusal The gate fails on a ground that names a pattern type that does not exist

Observation None, because a pattern type is a viewpoint on structure, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a ground whose kind exists and whose id does not, and a ground filed under the wrong kind, and passes a well-formed one

Authoritative side The pattern type list, which every ground that names a type cites

Depends on Not answered

Shape it refuses Not answered

dynamical

Details

change over time

How it is checked

Checked by the ontology resolution gate over every ground that names the pattern type

Population Every construct and record that grounds the pattern type

Freshness A verdict stands until the pattern types or a record that names one changes

Refusal The gate fails on a ground that names a pattern type that does not exist

Observation None, because a pattern type is a viewpoint on structure, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a ground whose kind exists and whose id does not, and a ground filed under the wrong kind, and passes a well-formed one

Authoritative side The pattern type list, which every ground that names a type cites

Depends on Not answered

Shape it refuses Not answered

computational

Details

procedures and algorithms

How it is checked

Checked by the ontology resolution gate over every ground that names the pattern type

Population Every construct and record that grounds the pattern type

Freshness A verdict stands until the pattern types or a record that names one changes

Refusal The gate fails on a ground that names a pattern type that does not exist

Observation None, because a pattern type is a viewpoint on structure, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a ground whose kind exists and whose id does not, and a ground filed under the wrong kind, and passes a well-formed one

Authoritative side The pattern type list, which every ground that names a type cites

Depends on Not answered

Shape it refuses Not answered

categorical

Details

relationships between structures

How it is checked

Checked by the ontology resolution gate over every ground that names the pattern type

Population Every construct and record that grounds the pattern type

Freshness A verdict stands until the pattern types or a record that names one changes

Refusal The gate fails on a ground that names a pattern type that does not exist

Observation None, because a pattern type is a viewpoint on structure, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a ground whose kind exists and whose id does not, and a ground filed under the wrong kind, and passes a well-formed one

Authoritative side The pattern type list, which every ground that names a type cites

Depends on Not answered

Shape it refuses Not answered

fractal

Details

recursive self-similarity

How it is checked

Checked by the ontology resolution gate over every ground that names the pattern type

Population Every construct and record that grounds the pattern type

Freshness A verdict stands until the pattern types or a record that names one changes

Refusal The gate fails on a ground that names a pattern type that does not exist

Observation None, because a pattern type is a viewpoint on structure, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a ground whose kind exists and whose id does not, and a ground filed under the wrong kind, and passes a well-formed one

Authoritative side The pattern type list, which every ground that names a type cites

Depends on Not answered

Shape it refuses Not answered

The models

The models are sequences that restate the same cycle from different starting points.

ontogenesis

  • Question: How does a pattern come to be?
  • Recursion: emergence β†’ difference

Details

Sequence existence β†’ difference β†’ relation β†’ structure β†’ transformation β†’ constraint β†’ emergence

How it is checked

Checked by the model-step check, which holds every step to the model's declared step kind, the document-type check, which requires every structured document type to name a model

Population Every model, its steps, and every document type that names it

Freshness A verdict stands until the model, its step kind or a document type that names it changes

Refusal The gate fails on a step outside the declared kind, or a document type whose model does not resolve

Observation None, because a model is a sequence of reasoning steps, and nothing observes it while a run executes

Evidence Watched to fire and to accept: one suite plants a step outside the model's step kind, another plants a document type whose model does not resolve, and the bundled data validates clean

Authoritative side The model's declared step kind, which each step conforms to, and the model, which a document type cites

Depends on Not answered

Shape it refuses Not answered

epistemology

  • Question: How is a pattern known?

Details

Sequence observation β†’ description β†’ comparison β†’ classification β†’ explanation β†’ prediction β†’ intervention β†’ creation β†’ reflection

How it is checked

Checked by the model-step check, which holds every step to the model's declared step kind, the document-type check, which requires every structured document type to name a model

Population Every model, its steps, and every document type that names it

Freshness A verdict stands until the model, its step kind or a document type that names it changes

Refusal The gate fails on a step outside the declared kind, or a document type whose model does not resolve

Observation None, because a model is a sequence of reasoning steps, and nothing observes it while a run executes

Evidence Watched to fire and to accept: one suite plants a step outside the model's step kind, another plants a document type whose model does not resolve, and the bundled data validates clean

Authoritative side The model's declared step kind, which each step conforms to, and the model, which a document type cites

Depends on Not answered

Shape it refuses Not answered

cognition

  • Question: How does a system perceive, act, and adapt?
  • Recursion: evolution β†’ difference

Details

Sequence existence β†’ difference β†’ relation β†’ structure β†’ transformation β†’ constraint β†’ emergence β†’ representation β†’ memory β†’ prediction β†’ action β†’ feedback β†’ evolution

How it is checked

Checked by the model-step check, which holds every step to the model's declared step kind, the document-type check, which requires every structured document type to name a model

Population Every model, its steps, and every document type that names it

Freshness A verdict stands until the model, its step kind or a document type that names it changes

Refusal The gate fails on a step outside the declared kind, or a document type whose model does not resolve

Observation None, because a model is a sequence of reasoning steps, and nothing observes it while a run executes

Evidence Watched to fire and to accept: one suite plants a step outside the model's step kind, another plants a document type whose model does not resolve, and the bundled data validates clean

Authoritative side The model's declared step kind, which each step conforms to, and the model, which a document type cites

Depends on Not answered

Shape it refuses Not answered

pattern-cycle

  • Question: How does pattern-work proceed?
  • Recursion: create β†’ exist

Details

Sequence exist β†’ differentiate β†’ relate β†’ organize β†’ transform β†’ constrain β†’ stabilize β†’ represent β†’ reasoning β†’ predict β†’ create

How it is checked

Checked by the model-step check, which holds every step to the model's declared step kind, the document-type check, which requires every structured document type to name a model

Population Every model, its steps, and every document type that names it

Freshness A verdict stands until the model, its step kind or a document type that names it changes

Refusal The gate fails on a step outside the declared kind, or a document type whose model does not resolve

Observation None, because a model is a sequence of reasoning steps, and nothing observes it while a run executes

Evidence Watched to fire and to accept: one suite plants a step outside the model's step kind, another plants a document type whose model does not resolve, and the bundled data validates clean

Authoritative side The model's declared step kind, which each step conforms to, and the model, which a document type cites

Depends on Not answered

Shape it refuses Not answered

The universal axes

The five universal axes are listed with the dimensions each one subsumes and the lenses that sit on it.

existence

Details

Question What entities are present?

Subsumes identity

How it is checked

Checked by the ontology resolution gate, which requires every lens to name a universal axis that exists

Population Every lens that names the universal axis

Freshness A verdict stands until the universal axes or a lens changes

Refusal The gate fails on a lens that names a universal axis that does not exist

Observation None, because a universal axis groups lenses, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a lens whose universal axis does not exist, and the bundled lenses validate clean

Authoritative side The universal axis list, which every lens cites

Depends on Not answered

Shape it refuses Not answered

arrangement

Details

Question How are they organized?

Subsumes structure, space

Lenses structural, spatial, invariant

How it is checked

Checked by the ontology resolution gate, which requires every lens to name a universal axis that exists

Population Every lens that names the universal axis

Freshness A verdict stands until the universal axes or a lens changes

Refusal The gate fails on a lens that names a universal axis that does not exist

Observation None, because a universal axis groups lenses, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a lens whose universal axis does not exist, and the bundled lenses validate clean

Authoritative side The universal axis list, which every lens cites

Depends on Not answered

Shape it refuses Not answered

dynamics

Details

Question How do they change?

Subsumes time, change

Lenses temporal, frequency, sequential, evolutionary, transformational

How it is checked

Checked by the ontology resolution gate, which requires every lens to name a universal axis that exists

Population Every lens that names the universal axis

Freshness A verdict stands until the universal axes or a lens changes

Refusal The gate fails on a lens that names a universal axis that does not exist

Observation None, because a universal axis groups lenses, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a lens whose universal axis does not exist, and the bundled lenses validate clean

Authoritative side The universal axis list, which every lens cites

Depends on Not answered

Shape it refuses Not answered

interaction

Details

Question How do they influence one another?

Subsumes relation, behavior, cause

Lenses relational, behavioral, causal

How it is checked

Checked by the ontology resolution gate, which requires every lens to name a universal axis that exists

Population Every lens that names the universal axis

Freshness A verdict stands until the universal axes or a lens changes

Refusal The gate fails on a lens that names a universal axis that does not exist

Observation None, because a universal axis groups lenses, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a lens whose universal axis does not exist, and the bundled lenses validate clean

Authoritative side The universal axis list, which every lens cites

Depends on Not answered

Shape it refuses Not answered

abstraction

Details

Question What meaning or principle can be inferred?

Subsumes meaning, function, probability

Lenses statistical, functional, semantic, predictive, anomaly, fractal, optimization, complexity

How it is checked

Checked by the ontology resolution gate, which requires every lens to name a universal axis that exists

Population Every lens that names the universal axis

Freshness A verdict stands until the universal axes or a lens changes

Refusal The gate fails on a lens that names a universal axis that does not exist

Observation None, because a universal axis groups lenses, and nothing observes it while a run executes

Evidence Watched to fire and to accept: a suite plants a lens whose universal axis does not exist, and the bundled lenses validate clean

Authoritative side The universal axis list, which every lens cites

Depends on Not answered

Shape it refuses Not answered

The test surfaces

The test surfaces are what a system can be wrong about. Each is a dimension seen through a lens, listed with the invariant that must hold, the techniques that observe it, the predicate and what grounds it, the evidence it requires and the verdicts it can return. The architecture page reads the same grid in what can drift, seen through how it drifts.

semantic-correctness

Details

Fit An output is correct when it signifies what the input asked for, so the surface compares the meaning of the result with the meaning expected.

Failure modes wrong value, incorrect algorithm, wrong computation

Techniques unit-testing, property-based-testing, differential-testing, assertion-checking

Predicate grounds ver-ground-truth

Evidence test-result Β· required

Evidence grounds ver-evidence

Verdicts pass, fail, unknown

Predicate

output(input) = expected(input)

How it is checked

Checked by the techniques each surface lists, whose results the surface's predicate and evidence decide, the covered-surfaces check, which validates every surface a module declares covered

Population Every module that declares the surface covered, and the code under that module

Freshness A verdict stands until the module's code, its declaration or the surface changes

Refusal The covered-surfaces check fails a module that declares an unknown surface; a surface whose evidence is empty stays unknown, never pass

Observation The runtime techniques among the surface's list, which locate failures without certifying their absence

Evidence Watched to fire and to accept: a suite plants a surface with no techniques, an empty verdict domain, a blank predicate and a colliding cell, and the bundled surfaces validate clean

Authoritative side The evidence the surface's techniques produce, which the verdict is decided from, so an empty evidence set leaves it unknown

Depends on Not answered

Shape it refuses Not answered

functional-correctness

Details

Fit A workflow fulfils its role through the actions it takes, so the surface reads the role from the transitions the system actually performs.

Failure modes invalid workflow, missing transition, incorrect business rule

Techniques integration-testing, model-checking

Predicate grounds ver-ground-truth

Evidence test-result Β· required

Evidence grounds ver-evidence

Verdicts pass, fail, unknown

Predicate

transition in allowedTransitions

How it is checked

Checked by the techniques each surface lists, whose results the surface's predicate and evidence decide, the covered-surfaces check, which validates every surface a module declares covered

Population Every module that declares the surface covered, and the code under that module

Freshness A verdict stands until the module's code, its declaration or the surface changes

Refusal The covered-surfaces check fails a module that declares an unknown surface; a surface whose evidence is empty stays unknown, never pass

Observation The runtime techniques among the surface's list, which locate failures without certifying their absence

Evidence Watched to fire and to accept: a suite plants a surface with no techniques, an empty verdict domain, a blank predicate and a colliding cell, and the bundled surfaces validate clean

Authoritative side The evidence the surface's techniques produce, which the verdict is decided from, so an empty evidence set leaves it unknown

Depends on Not answered

Shape it refuses Not answered

state-correctness

Details

Fit A state is valid only relative to the one before it, so the surface checks conditions in the order they occur.

Failure modes invalid state, broken state transitions, violated lifecycle rules

Techniques assertion-checking, property-based-testing

Predicate grounds ver-ground-truth

Evidence test-result Β· required

Evidence grounds ver-evidence

Verdicts pass, fail, unknown

Predicate

state[t+1] in next(state[t])

How it is checked

Checked by the techniques each surface lists, whose results the surface's predicate and evidence decide, the covered-surfaces check, which validates every surface a module declares covered

Population Every module that declares the surface covered, and the code under that module

Freshness A verdict stands until the module's code, its declaration or the surface changes

Refusal The covered-surfaces check fails a module that declares an unknown surface; a surface whose evidence is empty stays unknown, never pass

Observation The runtime techniques among the surface's list, which locate failures without certifying their absence

Evidence Watched to fire and to accept: a suite plants a surface with no techniques, an empty verdict domain, a blank predicate and a colliding cell, and the bundled surfaces validate clean

Authoritative side The evidence the surface's techniques produce, which the verdict is decided from, so an empty evidence set leaves it unknown

Depends on Not answered

Shape it refuses Not answered

interface-correctness

Details

Fit A contract is an arrangement of fields and types, so the surface compares the shape of a payload with the shape the contract declares.

Failure modes invalid input/output shape, schema mismatch, contract violation

Techniques runtime-validation, contract-testing

Predicate grounds ver-ground-truth

Evidence test-result Β· required

Evidence grounds ver-evidence

Verdicts pass, fail, unknown

Predicate

payload models declaredSchema

How it is checked

Checked by the techniques each surface lists, whose results the surface's predicate and evidence decide, the covered-surfaces check, which validates every surface a module declares covered

Population Every module that declares the surface covered, and the code under that module

Freshness A verdict stands until the module's code, its declaration or the surface changes

Refusal The covered-surfaces check fails a module that declares an unknown surface; a surface whose evidence is empty stays unknown, never pass

Observation The runtime techniques among the surface's list, which locate failures without certifying their absence

Evidence Watched to fire and to accept: a suite plants a surface with no techniques, an empty verdict domain, a blank predicate and a colliding cell, and the bundled surfaces validate clean

Authoritative side The evidence the surface's techniques produce, which the verdict is decided from, so an empty evidence set leaves it unknown

Depends on Not answered

Shape it refuses Not answered

interaction-correctness

Details

Fit An interaction is the connection between two components, so the surface checks each request against the response its counterpart owes.

Failure modes wrong API response, incorrect UI behavior, invalid component communication

Techniques end-to-end-testing, contract-testing, integration-testing

Predicate grounds ver-ground-truth

Evidence test-result Β· required

Evidence grounds ver-evidence

Verdicts pass, fail, unknown

Predicate

response = contract(request)

How it is checked

Checked by the techniques each surface lists, whose results the surface's predicate and evidence decide, the covered-surfaces check, which validates every surface a module declares covered

Population Every module that declares the surface covered, and the code under that module

Freshness A verdict stands until the module's code, its declaration or the surface changes

Refusal The covered-surfaces check fails a module that declares an unknown surface; a surface whose evidence is empty stays unknown, never pass

Observation The runtime techniques among the surface's list, which locate failures without certifying their absence

Evidence Watched to fire and to accept: a suite plants a surface with no techniques, an empty verdict domain, a blank predicate and a colliding cell, and the bundled surfaces validate clean

Authoritative side The evidence the surface's techniques produce, which the verdict is decided from, so an empty evidence set leaves it unknown

Depends on Not answered

Shape it refuses Not answered

temporal-correctness

Details

Fit Execution time is a duration measured across a run, so the surface compares elapsed time with the deadline.

Failure modes timeout, deadline miss, stale data, starvation

Techniques load-testing, monitoring, tracing

Predicate grounds ver-ground-truth

Evidence measurement Β· required

Evidence grounds ver-evidence

Verdicts pass, fail, unknown

Predicate

elapsed <= deadline

How it is checked

Checked by the techniques each surface lists, whose results the surface's predicate and evidence decide, the covered-surfaces check, which validates every surface a module declares covered

Population Every module that declares the surface covered, and the code under that module

Freshness A verdict stands until the module's code, its declaration or the surface changes

Refusal The covered-surfaces check fails a module that declares an unknown surface; a surface whose evidence is empty stays unknown, never pass

Observation The runtime techniques among the surface's list, which locate failures without certifying their absence

Evidence Watched to fire and to accept: a suite plants a surface with no techniques, an empty verdict domain, a blank predicate and a colliding cell, and the bundled surfaces validate clean

Authoritative side The evidence the surface's techniques produce, which the verdict is decided from, so an empty evidence set leaves it unknown

Depends on Not answered

Shape it refuses Not answered

concurrency-correctness

Details

Fit Concurrent code misbehaves only in particular interleavings, so the surface examines what the system does across the orderings time allows.

Failure modes race conditions, deadlocks, livelocks, ordering failures

Techniques stress-testing, deterministic-replay

Predicate grounds ver-ground-truth

Evidence runtime-observation Β· required

Evidence grounds ver-evidence

Verdicts pass, fail, unknown

Predicate

for-all interleavings: linearizable(history)

How it is checked

Checked by the techniques each surface lists, whose results the surface's predicate and evidence decide, the covered-surfaces check, which validates every surface a module declares covered

Population Every module that declares the surface covered, and the code under that module

Freshness A verdict stands until the module's code, its declaration or the surface changes

Refusal The covered-surfaces check fails a module that declares an unknown surface; a surface whose evidence is empty stays unknown, never pass

Observation The runtime techniques among the surface's list, which locate failures without certifying their absence

Evidence Watched to fire and to accept: a suite plants a surface with no techniques, an empty verdict domain, a blank predicate and a colliding cell, and the bundled surfaces validate clean

Authoritative side The evidence the surface's techniques produce, which the verdict is decided from, so an empty evidence set leaves it unknown

Depends on Not answered

Shape it refuses Not answered

memory-correctness

Details

Fit A leak shows as the live set growing in content over a long run, so the surface tracks what memory holds as the run develops.

Failure modes memory leaks, excessive allocation, fragmentation, retention bugs

Techniques heap-analysis, profiling

Predicate grounds ver-ground-truth

Evidence measurement Β· required

Evidence grounds ver-evidence

Verdicts pass, fail, unknown

Predicate

liveSet bounded as t grows and retained delta approaches 0

How it is checked

Checked by the techniques each surface lists, whose results the surface's predicate and evidence decide, the covered-surfaces check, which validates every surface a module declares covered

Population Every module that declares the surface covered, and the code under that module

Freshness A verdict stands until the module's code, its declaration or the surface changes

Refusal The covered-surfaces check fails a module that declares an unknown surface; a surface whose evidence is empty stays unknown, never pass

Observation The runtime techniques among the surface's list, which locate failures without certifying their absence

Evidence Watched to fire and to accept: a suite plants a surface with no techniques, an empty verdict domain, a blank predicate and a colliding cell, and the bundled surfaces validate clean

Authoritative side The evidence the surface's techniques produce, which the verdict is decided from, so an empty evidence set leaves it unknown

Depends on Not answered

Shape it refuses Not answered

resource-correctness

Details

Fit A handle leak is a resource the system acquires and never gives back, so the surface pairs each acquisition with its release.

Failure modes file/socket/connection/handle leaks

Techniques monitoring, assertion-checking

Predicate grounds ver-ground-truth

Evidence runtime-observation Β· required

Evidence grounds ver-evidence

Verdicts pass, fail, unknown

Predicate

acquired = released (no leaked handles)

How it is checked

Checked by the techniques each surface lists, whose results the surface's predicate and evidence decide, the covered-surfaces check, which validates every surface a module declares covered

Population Every module that declares the surface covered, and the code under that module

Freshness A verdict stands until the module's code, its declaration or the surface changes

Refusal The covered-surfaces check fails a module that declares an unknown surface; a surface whose evidence is empty stays unknown, never pass

Observation The runtime techniques among the surface's list, which locate failures without certifying their absence

Evidence Watched to fire and to accept: a suite plants a surface with no techniques, an empty verdict domain, a blank predicate and a colliding cell, and the bundled surfaces validate clean

Authoritative side The evidence the surface's techniques produce, which the verdict is decided from, so an empty evidence set leaves it unknown

Depends on Not answered

Shape it refuses Not answered

performance-correctness

Details

Fit Performance depends on load, and one request says little about it, so the surface reads latency and throughput as distributions over many requests.

Failure modes slow algorithms, excessive CPU, high latency, throughput degradation

Techniques profiling, load-testing

Predicate grounds ver-ground-truth

Evidence measurement Β· required

Evidence grounds ver-evidence

Verdicts pass, fail, unknown

Predicate

latency_p99 <= budget and throughput >= floor

How it is checked

Checked by the techniques each surface lists, whose results the surface's predicate and evidence decide, the covered-surfaces check, which validates every surface a module declares covered

Population Every module that declares the surface covered, and the code under that module

Freshness A verdict stands until the module's code, its declaration or the surface changes

Refusal The covered-surfaces check fails a module that declares an unknown surface; a surface whose evidence is empty stays unknown, never pass

Observation The runtime techniques among the surface's list, which locate failures without certifying their absence

Evidence Watched to fire and to accept: a suite plants a surface with no techniques, an empty verdict domain, a blank predicate and a colliding cell, and the bundled surfaces validate clean

Authoritative side The evidence the surface's techniques produce, which the verdict is decided from, so an empty evidence set leaves it unknown

Depends on Not answered

Shape it refuses Not answered

reliability-correctness

Details

Fit A crash is a rare departure from normal running, so the surface looks for the inputs and faults that make it likely.

Failure modes crashes, unhandled exceptions, process termination

Techniques chaos-testing, fault-injection, monitoring

Predicate grounds ver-ground-truth

Evidence runtime-observation Β· required

Evidence grounds ver-evidence

Verdicts pass, fail, unknown

Predicate

no input leads to an unhandled fault

How it is checked

Checked by the techniques each surface lists, whose results the surface's predicate and evidence decide, the covered-surfaces check, which validates every surface a module declares covered

Population Every module that declares the surface covered, and the code under that module

Freshness A verdict stands until the module's code, its declaration or the surface changes

Refusal The covered-surfaces check fails a module that declares an unknown surface; a surface whose evidence is empty stays unknown, never pass

Observation The runtime techniques among the surface's list, which locate failures without certifying their absence

Evidence Watched to fire and to accept: a suite plants a surface with no techniques, an empty verdict domain, a blank predicate and a colliding cell, and the bundled surfaces validate clean

Authoritative side The evidence the surface's techniques produce, which the verdict is decided from, so an empty evidence set leaves it unknown

Depends on Not answered

Shape it refuses Not answered

availability-correctness

Details

Fit Availability is the share of time the service answers, so the surface measures uptime over a period under a declared fault set.

Failure modes service outage, cascading failure, degraded service

Techniques chaos-testing, fault-injection

Predicate grounds ver-ground-truth

Evidence runtime-observation Β· required

Evidence grounds ver-evidence

Verdicts pass, fail, unknown

Predicate

uptime >= SLO under the declared fault set

How it is checked

Checked by the techniques each surface lists, whose results the surface's predicate and evidence decide, the covered-surfaces check, which validates every surface a module declares covered

Population Every module that declares the surface covered, and the code under that module

Freshness A verdict stands until the module's code, its declaration or the surface changes

Refusal The covered-surfaces check fails a module that declares an unknown surface; a surface whose evidence is empty stays unknown, never pass

Observation The runtime techniques among the surface's list, which locate failures without certifying their absence

Evidence Watched to fire and to accept: a suite plants a surface with no techniques, an empty verdict domain, a blank predicate and a colliding cell, and the bundled surfaces validate clean

Authoritative side The evidence the surface's techniques produce, which the verdict is decided from, so an empty evidence set leaves it unknown

Depends on Not answered

Shape it refuses Not answered

consistency-correctness

Details

Fit Replicas agree or drift as a population, so the surface compares the state of every copy with the others.

Failure modes stale cache, divergent replicas, invalid synchronization

Techniques differential-testing, assertion-checking

Predicate grounds ver-ground-truth

Evidence test-result Β· required

Evidence grounds ver-evidence

Verdicts pass, fail, unknown

Predicate

for-all replicas: converge(state)

How it is checked

Checked by the techniques each surface lists, whose results the surface's predicate and evidence decide, the covered-surfaces check, which validates every surface a module declares covered

Population Every module that declares the surface covered, and the code under that module

Freshness A verdict stands until the module's code, its declaration or the surface changes

Refusal The covered-surfaces check fails a module that declares an unknown surface; a surface whose evidence is empty stays unknown, never pass

Observation The runtime techniques among the surface's list, which locate failures without certifying their absence

Evidence Watched to fire and to accept: a suite plants a surface with no techniques, an empty verdict domain, a blank predicate and a colliding cell, and the bundled surfaces validate clean

Authoritative side The evidence the surface's techniques produce, which the verdict is decided from, so an empty evidence set leaves it unknown

Depends on Not answered

Shape it refuses Not answered

data-correctness

Details

Fit Persisted data is correct when each record is still the same record in the same shape, so the surface checks identity and layout across writes and migrations.

Failure modes corrupted persistence, invalid migrations, duplicate records

Techniques assertion-checking, integration-testing

Predicate grounds ver-ground-truth

Evidence test-result Β· required

Evidence grounds ver-evidence

Verdicts pass, fail, unknown

Predicate

persisted = written and migrate then inverse = identity

How it is checked

Checked by the techniques each surface lists, whose results the surface's predicate and evidence decide, the covered-surfaces check, which validates every surface a module declares covered

Population Every module that declares the surface covered, and the code under that module

Freshness A verdict stands until the module's code, its declaration or the surface changes

Refusal The covered-surfaces check fails a module that declares an unknown surface; a surface whose evidence is empty stays unknown, never pass

Observation The runtime techniques among the surface's list, which locate failures without certifying their absence

Evidence Watched to fire and to accept: a suite plants a surface with no techniques, an empty verdict domain, a blank predicate and a colliding cell, and the bundled surfaces validate clean

Authoritative side The evidence the surface's techniques produce, which the verdict is decided from, so an empty evidence set leaves it unknown

Depends on Not answered

Shape it refuses Not answered

numerical-correctness

Details

Fit Numbers fail at the edges of their range, so the surface looks for the magnitudes where a result overflows, loses precision or turns into NaN.

Failure modes overflow, precision loss, NaN propagation

Techniques property-based-testing, static-analysis

Predicate grounds ver-ground-truth

Evidence analysis-report Β· required

Evidence grounds ver-evidence

Verdicts pass, fail, unknown

Predicate

result is finite and not overflow and not NaN

How it is checked

Checked by the techniques each surface lists, whose results the surface's predicate and evidence decide, the covered-surfaces check, which validates every surface a module declares covered

Population Every module that declares the surface covered, and the code under that module

Freshness A verdict stands until the module's code, its declaration or the surface changes

Refusal The covered-surfaces check fails a module that declares an unknown surface; a surface whose evidence is empty stays unknown, never pass

Observation The runtime techniques among the surface's list, which locate failures without certifying their absence

Evidence Watched to fire and to accept: a suite plants a surface with no techniques, an empty verdict domain, a blank predicate and a colliding cell, and the bundled surfaces validate clean

Authoritative side The evidence the surface's techniques produce, which the verdict is decided from, so an empty evidence set leaves it unknown

Depends on Not answered

Shape it refuses Not answered

security-correctness

Details

Fit An exploit is a chain from an input to an effect the boundary should prevent, so the surface traces what each input can cause.

Failure modes injection, privilege escalation, unsafe deserialization

Techniques static-analysis, fuzz-testing

Predicate grounds ver-ground-truth

Evidence analysis-report Β· required

Evidence grounds ver-evidence

Verdicts pass, fail, unknown

Predicate

no input yields privilege escalation or injection

How it is checked

Checked by the techniques each surface lists, whose results the surface's predicate and evidence decide, the covered-surfaces check, which validates every surface a module declares covered

Population Every module that declares the surface covered, and the code under that module

Freshness A verdict stands until the module's code, its declaration or the surface changes

Refusal The covered-surfaces check fails a module that declares an unknown surface; a surface whose evidence is empty stays unknown, never pass

Observation The runtime techniques among the surface's list, which locate failures without certifying their absence

Evidence Watched to fire and to accept: a suite plants a surface with no techniques, an empty verdict domain, a blank predicate and a colliding cell, and the bundled surfaces validate clean

Authoritative side The evidence the surface's techniques produce, which the verdict is decided from, so an empty evidence set leaves it unknown

Depends on Not answered

Shape it refuses Not answered

determinism-correctness

Details

Fit Nondeterminism appears as an output that differs from the one expected for the same input, so the surface repeats runs and looks for the deviation.

Failure modes the same input producing different outputs

Techniques property-based-testing, deterministic-replay

Predicate grounds ver-ground-truth

Evidence test-result Β· required

Evidence grounds ver-evidence

Verdicts pass, fail, unknown

Predicate

f(x) = f(x) across runs

How it is checked

Checked by the techniques each surface lists, whose results the surface's predicate and evidence decide, the covered-surfaces check, which validates every surface a module declares covered

Population Every module that declares the surface covered, and the code under that module

Freshness A verdict stands until the module's code, its declaration or the surface changes

Refusal The covered-surfaces check fails a module that declares an unknown surface; a surface whose evidence is empty stays unknown, never pass

Observation The runtime techniques among the surface's list, which locate failures without certifying their absence

Evidence Watched to fire and to accept: a suite plants a surface with no techniques, an empty verdict domain, a blank predicate and a colliding cell, and the bundled surfaces validate clean

Authoritative side The evidence the surface's techniques produce, which the verdict is decided from, so an empty evidence set leaves it unknown

Depends on Not answered

Shape it refuses Not answered

protocol-correctness

Details

Fit A protocol is a relation between parties that holds only in a given order of messages, so the surface checks the sequence against the protocol's grammar.

Failure modes invalid message ordering, malformed communication sequence

Techniques contract-testing, model-checking

Predicate grounds ver-ground-truth

Evidence test-result Β· required

Evidence grounds ver-evidence

Verdicts pass, fail, unknown

Predicate

messageSeq in protocolGrammar

How it is checked

Checked by the techniques each surface lists, whose results the surface's predicate and evidence decide, the covered-surfaces check, which validates every surface a module declares covered

Population Every module that declares the surface covered, and the code under that module

Freshness A verdict stands until the module's code, its declaration or the surface changes

Refusal The covered-surfaces check fails a module that declares an unknown surface; a surface whose evidence is empty stays unknown, never pass

Observation The runtime techniques among the surface's list, which locate failures without certifying their absence

Evidence Watched to fire and to accept: a suite plants a surface with no techniques, an empty verdict domain, a blank predicate and a colliding cell, and the bundled surfaces validate clean

Authoritative side The evidence the surface's techniques produce, which the verdict is decided from, so an empty evidence set leaves it unknown

Depends on Not answered

Shape it refuses Not answered

configuration-correctness

Details

Fit Configuration is the condition a deployment starts in, and it is valid when its keys and values take the declared shape, so the surface checks it against its schema.

Failure modes invalid environment variables, feature flag errors, deployment mismatch

Techniques runtime-validation, static-analysis

Predicate grounds ver-ground-truth

Evidence analysis-report Β· required

Evidence grounds ver-evidence

Verdicts pass, fail, unknown

Predicate

config models configSchema

How it is checked

Checked by the techniques each surface lists, whose results the surface's predicate and evidence decide, the covered-surfaces check, which validates every surface a module declares covered

Population Every module that declares the surface covered, and the code under that module

Freshness A verdict stands until the module's code, its declaration or the surface changes

Refusal The covered-surfaces check fails a module that declares an unknown surface; a surface whose evidence is empty stays unknown, never pass

Observation The runtime techniques among the surface's list, which locate failures without certifying their absence

Evidence Watched to fire and to accept: a suite plants a surface with no techniques, an empty verdict domain, a blank predicate and a colliding cell, and the bundled surfaces validate clean

Authoritative side The evidence the surface's techniques produce, which the verdict is decided from, so an empty evidence set leaves it unknown

Depends on Not answered

Shape it refuses Not answered

observability-correctness

Details

Fit A signal is accurate when every event it stands for is emitted each time the event occurs, so the surface compares how often events happen with how often they are reported.

Failure modes missing logs, incorrect metrics, broken traces

Techniques monitoring, tracing

Predicate grounds ver-ground-truth

Evidence runtime-observation Β· required

Evidence grounds ver-evidence

Verdicts pass, fail, unknown

Predicate

for-all event: emitted and measurable

How it is checked

Checked by the techniques each surface lists, whose results the surface's predicate and evidence decide, the covered-surfaces check, which validates every surface a module declares covered

Population Every module that declares the surface covered, and the code under that module

Freshness A verdict stands until the module's code, its declaration or the surface changes

Refusal The covered-surfaces check fails a module that declares an unknown surface; a surface whose evidence is empty stays unknown, never pass

Observation The runtime techniques among the surface's list, which locate failures without certifying their absence

Evidence Watched to fire and to accept: a suite plants a surface with no techniques, an empty verdict domain, a blank predicate and a colliding cell, and the bundled surfaces validate clean

Authoritative side The evidence the surface's techniques produce, which the verdict is decided from, so an empty evidence set leaves it unknown

Depends on Not answered

Shape it refuses Not answered

The techniques

Each technique a surface is observed by works in one reasoning mode and is listed with the surfaces that use it.

static-analysis

Details

Principle Reads structure and types for defects before execution

Refused by rules Static Analysis

Goes silent when Reports nothing when its rule never visits the construct, as with a misspelled visitor key

Surfaces numerical-correctness, security-correctness, configuration-correctness

How it is checked

Checked by the test surfaces that list the technique, whose predicates decide what a run of the technique shows

Population Every surface that lists the technique, and the code those surfaces cover

Freshness A verdict stands until the technique, a surface that lists it or the covered code changes

Refusal The gate fails a surface that lists an unknown technique, and a technique that states no way it fails

Observation The technique's own runs, which locate failures; its fails field names the way it goes silent

Evidence Watched to fire and to accept: one suite plants a surface that lists an unknown technique, another plants a technique that states no way it fails, and the bundled data validates clean

Authoritative side The technique record, which every surface that lists it cites

Depends on Not answered

Shape it refuses Not answered

unit-testing

Details

Principle Compares observed with expected results on an isolated unit

Goes silent when Passes when the doubles that isolate the unit no longer behave like the real collaborators

Surfaces semantic-correctness

How it is checked

Checked by the test surfaces that list the technique, whose predicates decide what a run of the technique shows

Population Every surface that lists the technique, and the code those surfaces cover

Freshness A verdict stands until the technique, a surface that lists it or the covered code changes

Refusal The gate fails a surface that lists an unknown technique, and a technique that states no way it fails

Observation The technique's own runs, which locate failures; its fails field names the way it goes silent

Evidence Watched to fire and to accept: one suite plants a surface that lists an unknown technique, another plants a technique that states no way it fails, and the bundled data validates clean

Authoritative side The technique record, which every surface that lists it cites

Depends on Not answered

Shape it refuses Not answered

integration-testing

Details

Principle Compares observed with expected results across cooperating parts

Goes silent when Passes on an environment that differs from production in the part that fails

Surfaces functional-correctness, interaction-correctness, data-correctness

How it is checked

Checked by the test surfaces that list the technique, whose predicates decide what a run of the technique shows

Population Every surface that lists the technique, and the code those surfaces cover

Freshness A verdict stands until the technique, a surface that lists it or the covered code changes

Refusal The gate fails a surface that lists an unknown technique, and a technique that states no way it fails

Observation The technique's own runs, which locate failures; its fails field names the way it goes silent

Evidence Watched to fire and to accept: one suite plants a surface that lists an unknown technique, another plants a technique that states no way it fails, and the bundled data validates clean

Authoritative side The technique record, which every surface that lists it cites

Depends on Not answered

Shape it refuses Not answered

end-to-end-testing

Details

Principle Compares observed with expected results on the whole system

Goes silent when Is retried until it passes, so an intermittent failure is read as noise

Surfaces interaction-correctness

How it is checked

Checked by the test surfaces that list the technique, whose predicates decide what a run of the technique shows

Population Every surface that lists the technique, and the code those surfaces cover

Freshness A verdict stands until the technique, a surface that lists it or the covered code changes

Refusal The gate fails a surface that lists an unknown technique, and a technique that states no way it fails

Observation The technique's own runs, which locate failures; its fails field names the way it goes silent

Evidence Watched to fire and to accept: one suite plants a surface that lists an unknown technique, another plants a technique that states no way it fails, and the bundled data validates clean

Authoritative side The technique record, which every surface that lists it cites

Depends on Not answered

Shape it refuses Not answered

property-based-testing

Details

Principle Asserts that an invariant holds across a generated input space

Refused by rules Property-Based Testing

Goes silent when Passes when the generator never produces the inputs that break the property

Surfaces semantic-correctness, state-correctness, numerical-correctness, determinism-correctness

How it is checked

Checked by the test surfaces that list the technique, whose predicates decide what a run of the technique shows

Population Every surface that lists the technique, and the code those surfaces cover

Freshness A verdict stands until the technique, a surface that lists it or the covered code changes

Refusal The gate fails a surface that lists an unknown technique, and a technique that states no way it fails

Observation The technique's own runs, which locate failures; its fails field names the way it goes silent

Evidence Watched to fire and to accept: one suite plants a surface that lists an unknown technique, another plants a technique that states no way it fails, and the bundled data validates clean

Authoritative side The technique record, which every surface that lists it cites

Depends on Not answered

Shape it refuses Not answered

differential-testing

Details

Principle Compares observed results with a reference implementation, the oracle

Goes silent when Passes when the reference implementation shares the defect

Surfaces semantic-correctness, consistency-correctness

How it is checked

Checked by the test surfaces that list the technique, whose predicates decide what a run of the technique shows

Population Every surface that lists the technique, and the code those surfaces cover

Freshness A verdict stands until the technique, a surface that lists it or the covered code changes

Refusal The gate fails a surface that lists an unknown technique, and a technique that states no way it fails

Observation The technique's own runs, which locate failures; its fails field names the way it goes silent

Evidence Watched to fire and to accept: one suite plants a surface that lists an unknown technique, another plants a technique that states no way it fails, and the bundled data validates clean

Authoritative side The technique record, which every surface that lists it cites

Depends on Not answered

Shape it refuses Not answered

contract-testing

Details

Principle Compares an observed interface with an agreed contract

Goes silent when Passes against a copy of the contract that drifted from the one the provider serves

Surfaces interface-correctness, interaction-correctness, protocol-correctness

How it is checked

Checked by the test surfaces that list the technique, whose predicates decide what a run of the technique shows

Population Every surface that lists the technique, and the code those surfaces cover

Freshness A verdict stands until the technique, a surface that lists it or the covered code changes

Refusal The gate fails a surface that lists an unknown technique, and a technique that states no way it fails

Observation The technique's own runs, which locate failures; its fails field names the way it goes silent

Evidence Watched to fire and to accept: one suite plants a surface that lists an unknown technique, another plants a technique that states no way it fails, and the bundled data validates clean

Authoritative side The technique record, which every surface that lists it cites

Depends on Not answered

Shape it refuses Not answered

runtime-validation

Details

Principle Checks boundary data against its declared shape at runtime

Goes silent when Never runs on a path that reaches the core without crossing the boundary

Surfaces interface-correctness, configuration-correctness

How it is checked

Checked by the test surfaces that list the technique, whose predicates decide what a run of the technique shows

Population Every surface that lists the technique, and the code those surfaces cover

Freshness A verdict stands until the technique, a surface that lists it or the covered code changes

Refusal The gate fails a surface that lists an unknown technique, and a technique that states no way it fails

Observation The technique's own runs, which locate failures; its fails field names the way it goes silent

Evidence Watched to fire and to accept: one suite plants a surface that lists an unknown technique, another plants a technique that states no way it fails, and the bundled data validates clean

Authoritative side The technique record, which every surface that lists it cites

Depends on Not answered

Shape it refuses Not answered

assertion-checking

Details

Principle Checks a runtime condition against an assumed invariant

Goes silent when Is compiled out or disabled in the build that runs in production

Surfaces semantic-correctness, state-correctness, resource-correctness, consistency-correctness, data-correctness

How it is checked

Checked by the test surfaces that list the technique, whose predicates decide what a run of the technique shows

Population Every surface that lists the technique, and the code those surfaces cover

Freshness A verdict stands until the technique, a surface that lists it or the covered code changes

Refusal The gate fails a surface that lists an unknown technique, and a technique that states no way it fails

Observation The technique's own runs, which locate failures; its fails field names the way it goes silent

Evidence Watched to fire and to accept: one suite plants a surface that lists an unknown technique, another plants a technique that states no way it fails, and the bundled data validates clean

Authoritative side The technique record, which every surface that lists it cites

Depends on Not answered

Shape it refuses Not answered

fuzz-testing

Details

Principle Generates adversarial inputs to provoke unhandled failures

Goes silent when Stops before the generated inputs reach the failing region, and the run reports no crash

Surfaces security-correctness

How it is checked

Checked by the test surfaces that list the technique, whose predicates decide what a run of the technique shows

Population Every surface that lists the technique, and the code those surfaces cover

Freshness A verdict stands until the technique, a surface that lists it or the covered code changes

Refusal The gate fails a surface that lists an unknown technique, and a technique that states no way it fails

Observation The technique's own runs, which locate failures; its fails field names the way it goes silent

Evidence Watched to fire and to accept: one suite plants a surface that lists an unknown technique, another plants a technique that states no way it fails, and the bundled data validates clean

Authoritative side The technique record, which every surface that lists it cites

Depends on Not answered

Shape it refuses Not answered

load-testing

Details

Principle Projects behavior under expected demand

Goes silent when Runs a workload shaped unlike real demand

Surfaces temporal-correctness, performance-correctness

How it is checked

Checked by the test surfaces that list the technique, whose predicates decide what a run of the technique shows

Population Every surface that lists the technique, and the code those surfaces cover

Freshness A verdict stands until the technique, a surface that lists it or the covered code changes

Refusal The gate fails a surface that lists an unknown technique, and a technique that states no way it fails

Observation The technique's own runs, which locate failures; its fails field names the way it goes silent

Evidence Watched to fire and to accept: one suite plants a surface that lists an unknown technique, another plants a technique that states no way it fails, and the bundled data validates clean

Authoritative side The technique record, which every surface that lists it cites

Depends on Not answered

Shape it refuses Not answered

stress-testing

Details

Principle Projects behavior past its limits to expose timing and ordering defects

Goes silent when Ends at a limit below the one production reaches

Surfaces concurrency-correctness

How it is checked

Checked by the test surfaces that list the technique, whose predicates decide what a run of the technique shows

Population Every surface that lists the technique, and the code those surfaces cover

Freshness A verdict stands until the technique, a surface that lists it or the covered code changes

Refusal The gate fails a surface that lists an unknown technique, and a technique that states no way it fails

Observation The technique's own runs, which locate failures; its fails field names the way it goes silent

Evidence Watched to fire and to accept: one suite plants a surface that lists an unknown technique, another plants a technique that states no way it fails, and the bundled data validates clean

Authoritative side The technique record, which every surface that lists it cites

Depends on Not answered

Shape it refuses Not answered

profiling

Details

Principle Measures the distribution of execution cost

Refused by rules Profiling

Goes silent when Samples too coarsely to see a short, frequent cost

Surfaces memory-correctness, performance-correctness

How it is checked

Checked by the test surfaces that list the technique, whose predicates decide what a run of the technique shows

Population Every surface that lists the technique, and the code those surfaces cover

Freshness A verdict stands until the technique, a surface that lists it or the covered code changes

Refusal The gate fails a surface that lists an unknown technique, and a technique that states no way it fails

Observation The technique's own runs, which locate failures; its fails field names the way it goes silent

Evidence Watched to fire and to accept: one suite plants a surface that lists an unknown technique, another plants a technique that states no way it fails, and the bundled data validates clean

Authoritative side The technique record, which every surface that lists it cites

Depends on Not answered

Shape it refuses Not answered

heap-analysis

Details

Principle Measures allocation and retention over time

Goes silent when Measures a run too short for retention to show

Surfaces memory-correctness

How it is checked

Checked by the test surfaces that list the technique, whose predicates decide what a run of the technique shows

Population Every surface that lists the technique, and the code those surfaces cover

Freshness A verdict stands until the technique, a surface that lists it or the covered code changes

Refusal The gate fails a surface that lists an unknown technique, and a technique that states no way it fails

Observation The technique's own runs, which locate failures; its fails field names the way it goes silent

Evidence Watched to fire and to accept: one suite plants a surface that lists an unknown technique, another plants a technique that states no way it fails, and the bundled data validates clean

Authoritative side The technique record, which every surface that lists it cites

Depends on Not answered

Shape it refuses Not answered

tracing

Details

Principle Describes the runtime flow across components

Goes silent when Loses spans at an uninstrumented hop, and the trace reads as complete

Surfaces temporal-correctness, observability-correctness

How it is checked

Checked by the test surfaces that list the technique, whose predicates decide what a run of the technique shows

Population Every surface that lists the technique, and the code those surfaces cover

Freshness A verdict stands until the technique, a surface that lists it or the covered code changes

Refusal The gate fails a surface that lists an unknown technique, and a technique that states no way it fails

Observation The technique's own runs, which locate failures; its fails field names the way it goes silent

Evidence Watched to fire and to accept: one suite plants a surface that lists an unknown technique, another plants a technique that states no way it fails, and the bundled data validates clean

Authoritative side The technique record, which every surface that lists it cites

Depends on Not answered

Shape it refuses Not answered

fault-injection

Details

Principle Induces a failure and observes the response

Goes silent when Injects only the faults the developer anticipated

Surfaces reliability-correctness, availability-correctness

How it is checked

Checked by the test surfaces that list the technique, whose predicates decide what a run of the technique shows

Population Every surface that lists the technique, and the code those surfaces cover

Freshness A verdict stands until the technique, a surface that lists it or the covered code changes

Refusal The gate fails a surface that lists an unknown technique, and a technique that states no way it fails

Observation The technique's own runs, which locate failures; its fails field names the way it goes silent

Evidence Watched to fire and to accept: one suite plants a surface that lists an unknown technique, another plants a technique that states no way it fails, and the bundled data validates clean

Authoritative side The technique record, which every surface that lists it cites

Depends on Not answered

Shape it refuses Not answered

chaos-testing

Details

Principle Induces random failures and observes how the system recovers

Goes silent when Runs where the dependency that fails in production is absent

Surfaces reliability-correctness, availability-correctness

How it is checked

Checked by the test surfaces that list the technique, whose predicates decide what a run of the technique shows

Population Every surface that lists the technique, and the code those surfaces cover

Freshness A verdict stands until the technique, a surface that lists it or the covered code changes

Refusal The gate fails a surface that lists an unknown technique, and a technique that states no way it fails

Observation The technique's own runs, which locate failures; its fails field names the way it goes silent

Evidence Watched to fire and to accept: one suite plants a surface that lists an unknown technique, another plants a technique that states no way it fails, and the bundled data validates clean

Authoritative side The technique record, which every surface that lists it cites

Depends on Not answered

Shape it refuses Not answered

model-checking

Details

Principle Proves that a property holds across the reachable state space

Goes silent when Proves the model while the code drifts away from it

Surfaces functional-correctness, protocol-correctness

How it is checked

Checked by the test surfaces that list the technique, whose predicates decide what a run of the technique shows

Population Every surface that lists the technique, and the code those surfaces cover

Freshness A verdict stands until the technique, a surface that lists it or the covered code changes

Refusal The gate fails a surface that lists an unknown technique, and a technique that states no way it fails

Observation The technique's own runs, which locate failures; its fails field names the way it goes silent

Evidence Watched to fire and to accept: one suite plants a surface that lists an unknown technique, another plants a technique that states no way it fails, and the bundled data validates clean

Authoritative side The technique record, which every surface that lists it cites

Depends on Not answered

Shape it refuses Not answered

deterministic-replay

Details

Principle Reproduces a run to isolate a non-deterministic cause

Goes silent when Replays a recording that left out the source of the non-determinism

Surfaces concurrency-correctness, determinism-correctness

How it is checked

Checked by the test surfaces that list the technique, whose predicates decide what a run of the technique shows

Population Every surface that lists the technique, and the code those surfaces cover

Freshness A verdict stands until the technique, a surface that lists it or the covered code changes

Refusal The gate fails a surface that lists an unknown technique, and a technique that states no way it fails

Observation The technique's own runs, which locate failures; its fails field names the way it goes silent

Evidence Watched to fire and to accept: one suite plants a surface that lists an unknown technique, another plants a technique that states no way it fails, and the bundled data validates clean

Authoritative side The technique record, which every surface that lists it cites

Depends on Not answered

Shape it refuses Not answered

monitoring

Details

Principle Observes live behavior for deviations from normal

Refused by rules Monitoring

Goes silent when Reports no deviation because the signal it watches was never emitted

Surfaces temporal-correctness, resource-correctness, reliability-correctness, observability-correctness

How it is checked

Checked by the test surfaces that list the technique, whose predicates decide what a run of the technique shows

Population Every surface that lists the technique, and the code those surfaces cover

Freshness A verdict stands until the technique, a surface that lists it or the covered code changes

Refusal The gate fails a surface that lists an unknown technique, and a technique that states no way it fails

Observation The technique's own runs, which locate failures; its fails field names the way it goes silent

Evidence Watched to fire and to accept: one suite plants a surface that lists an unknown technique, another plants a technique that states no way it fails, and the bundled data validates clean

Authoritative side The technique record, which every surface that lists it cites

Depends on Not answered

Shape it refuses Not answered

mutation-testing

Details

Principle Introduces a deliberate defect and checks that the tests or the rule report it

Goes silent when Counts a mutant as caught by a test that fails for an unrelated reason

How it is checked

Checked by the test surfaces that list the technique, whose predicates decide what a run of the technique shows

Population Every surface that lists the technique, and the code those surfaces cover

Freshness A verdict stands until the technique, a surface that lists it or the covered code changes

Refusal The gate fails a surface that lists an unknown technique, and a technique that states no way it fails

Observation The technique's own runs, which locate failures; its fails field names the way it goes silent

Evidence Watched to fire and to accept: one suite plants a surface that lists an unknown technique, another plants a technique that states no way it fails, and the bundled data validates clean

Authoritative side The technique record, which every surface that lists it cites

Depends on Not answered

Shape it refuses Not answered

read-after-write-verification

Details

Principle Reads back what was written and compares it with what was meant to be written

Goes silent when Reads from a cache or a buffer instead of the store the write reached

How it is checked

Checked by the test surfaces that list the technique, whose predicates decide what a run of the technique shows

Population Every surface that lists the technique, and the code those surfaces cover

Freshness A verdict stands until the technique, a surface that lists it or the covered code changes

Refusal The gate fails a surface that lists an unknown technique, and a technique that states no way it fails

Observation The technique's own runs, which locate failures; its fails field names the way it goes silent

Evidence Watched to fire and to accept: one suite plants a surface that lists an unknown technique, another plants a technique that states no way it fails, and the bundled data validates clean

Authoritative side The technique record, which every surface that lists it cites

Depends on Not answered

Shape it refuses Not answered

The invariants

Each invariant the test surfaces assert is listed with the surfaces that assert it.

Correct Outputs

Details

Invariant Outputs are correct

Surfaces semantic-correctness, data-correctness

How it is checked

Checked by the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground

Population Every test surface and document construct that names the invariant

Freshness A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes

Refusal The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause

Observation The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence

Evidence Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean

Authoritative side The invariant record, which every surface and document construct that asserts it cites

Depends on Not answered

Shape it refuses Not answered

Correct State Evolution

Details

Invariant State evolves correctly

Surfaces functional-correctness

How it is checked

Checked by the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground

Population Every test surface and document construct that names the invariant

Freshness A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes

Refusal The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause

Observation The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence

Evidence Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean

Authoritative side The invariant record, which every surface and document construct that asserts it cites

Depends on Not answered

Shape it refuses Not answered

Valid State Transitions

Details

Invariant State transitions are valid

Surfaces state-correctness

How it is checked

Checked by the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground

Population Every test surface and document construct that names the invariant

Freshness A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes

Refusal The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause

Observation The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence

Evidence Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean

Authoritative side The invariant record, which every surface and document construct that asserts it cites

Depends on Not answered

Shape it refuses Not answered

Correct Interactions

Details

Invariant Interactions between components are correct

Surfaces interaction-correctness

How it is checked

Checked by the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground

Population Every test surface and document construct that names the invariant

Freshness A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes

Refusal The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause

Observation The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence

Evidence Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean

Authoritative side The invariant record, which every surface and document construct that asserts it cites

Depends on Not answered

Shape it refuses Not answered

Valid Interfaces and Contracts

Details

Invariant Interfaces and contracts are valid

Surfaces interface-correctness

How it is checked

Checked by the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground

Population Every test surface and document construct that names the invariant

Freshness A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes

Refusal The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause

Observation The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence

Evidence Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean

Authoritative side The invariant record, which every surface and document construct that asserts it cites

Depends on Not answered

Shape it refuses Not answered

Acceptable Execution Time

Details

Invariant Execution time is acceptable

Surfaces temporal-correctness, performance-correctness

How it is checked

Checked by the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground

Population Every test surface and document construct that names the invariant

Freshness A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes

Refusal The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause

Observation The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence

Evidence Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean

Authoritative side The invariant record, which every surface and document construct that asserts it cites

Depends on Not answered

Shape it refuses Not answered

Acceptable Resource Consumption

Details

Invariant Resource consumption is acceptable

Surfaces resource-correctness

How it is checked

Checked by the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground

Population Every test surface and document construct that names the invariant

Freshness A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes

Refusal The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause

Observation The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence

Evidence Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean

Authoritative side The invariant record, which every surface and document construct that asserts it cites

Depends on Not answered

Shape it refuses Not answered

Safe Concurrent Behavior

Details

Invariant Concurrent behavior is safe

Surfaces concurrency-correctness

How it is checked

Checked by the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground

Population Every test surface and document construct that names the invariant

Freshness A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes

Refusal The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause

Observation The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence

Evidence Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean

Authoritative side The invariant record, which every surface and document construct that asserts it cites

Depends on Not answered

Shape it refuses Not answered

Controlled Memory Usage

Details

Invariant Memory usage is controlled

Surfaces memory-correctness

How it is checked

Checked by the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground

Population Every test surface and document construct that names the invariant

Freshness A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes

Refusal The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause

Observation The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence

Evidence Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean

Authoritative side The invariant record, which every surface and document construct that asserts it cites

Depends on Not answered

Shape it refuses Not answered

Reliability Under Faults

Details

Invariant The system stays reliable under faults

Surfaces reliability-correctness

How it is checked

Checked by the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground

Population Every test surface and document construct that names the invariant

Freshness A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes

Refusal The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause

Observation The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence

Evidence Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean

Authoritative side The invariant record, which every surface and document construct that asserts it cites

Depends on Not answered

Shape it refuses Not answered

Availability Under Stress

Details

Invariant The system stays available under stress

Surfaces availability-correctness

How it is checked

Checked by the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground

Population Every test surface and document construct that names the invariant

Freshness A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes

Refusal The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause

Observation The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence

Evidence Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean

Authoritative side The invariant record, which every surface and document construct that asserts it cites

Depends on Not answered

Shape it refuses Not answered

Consistency Across Components

Details

Invariant Components stay consistent with each other

Surfaces consistency-correctness

How it is checked

Checked by the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground

Population Every test surface and document construct that names the invariant

Freshness A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes

Refusal The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause

Observation The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence

Evidence Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean

Authoritative side The invariant record, which every surface and document construct that asserts it cites

Depends on Not answered

Shape it refuses Not answered

Required Determinism

Details

Invariant Behavior is deterministic where determinism is required

Surfaces determinism-correctness

How it is checked

Checked by the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground

Population Every test surface and document construct that names the invariant

Freshness A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes

Refusal The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause

Observation The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence

Evidence Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean

Authoritative side The invariant record, which every surface and document construct that asserts it cites

Depends on Not answered

Shape it refuses Not answered

Numerical Validity

Details

Invariant Numerical results are valid

Surfaces numerical-correctness

How it is checked

Checked by the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground

Population Every test surface and document construct that names the invariant

Freshness A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes

Refusal The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause

Observation The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence

Evidence Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean

Authoritative side The invariant record, which every surface and document construct that asserts it cites

Depends on Not answered

Shape it refuses Not answered

Security Boundaries

Details

Invariant Security boundaries hold

Surfaces security-correctness

How it is checked

Checked by the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground

Population Every test surface and document construct that names the invariant

Freshness A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes

Refusal The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause

Observation The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence

Evidence Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean

Authoritative side The invariant record, which every surface and document construct that asserts it cites

Depends on Not answered

Shape it refuses Not answered

Protocol Compliance

Details

Invariant Communication complies with its protocol

Surfaces protocol-correctness

How it is checked

Checked by the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground

Population Every test surface and document construct that names the invariant

Freshness A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes

Refusal The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause

Observation The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence

Evidence Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean

Authoritative side The invariant record, which every surface and document construct that asserts it cites

Depends on Not answered

Shape it refuses Not answered

Configuration Validity

Details

Invariant Configuration is valid

Surfaces configuration-correctness

How it is checked

Checked by the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground

Population Every test surface and document construct that names the invariant

Freshness A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes

Refusal The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause

Observation The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence

Evidence Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean

Authoritative side The invariant record, which every surface and document construct that asserts it cites

Depends on Not answered

Shape it refuses Not answered

Accurate Observability

Details

Invariant Logs, metrics and traces report the system accurately

Surfaces observability-correctness

How it is checked

Checked by the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground

Population Every test surface and document construct that names the invariant

Freshness A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes

Refusal The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause

Observation The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence

Evidence Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean

Authoritative side The invariant record, which every surface and document construct that asserts it cites

Depends on Not answered

Shape it refuses Not answered

Reachable Check

Details

Invariant Every representation in jurisdiction has a computable check

Grounded by meta_field

How it is checked

Checked by the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground

Population Every test surface and document construct that names the invariant

Freshness A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes

Refusal The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause

Observation The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence

Evidence Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean

Authoritative side The invariant record, which every surface and document construct that asserts it cites

Depends on Not answered

Shape it refuses Not answered

Declared Domain

Details

Invariant A check's domain is explicit and reported beside its verdict

How it is checked

Checked by the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground

Population Every test surface and document construct that names the invariant

Freshness A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes

Refusal The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause

Observation The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence

Evidence Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean

Authoritative side The invariant record, which every surface and document construct that asserts it cites

Depends on Not answered

Shape it refuses Not answered

Declared Dependency

Details

Invariant A dependency is declared by the referent, never inferred from a name

Grounded by dag_declaration, edge_clause

How it is checked

Checked by the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground

Population Every test surface and document construct that names the invariant

Freshness A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes

Refusal The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause

Observation The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence

Evidence Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean

Authoritative side The invariant record, which every surface and document construct that asserts it cites

Depends on Not answered

Shape it refuses Not answered

Checked Verdict

Details

Invariant A verdict is itself a representation and has a reachable check of its own

Grounded by report_block

How it is checked

Checked by the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground

Population Every test surface and document construct that names the invariant

Freshness A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes

Refusal The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause

Observation The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence

Evidence Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean

Authoritative side The invariant record, which every surface and document construct that asserts it cites

Depends on Not answered

Shape it refuses Not answered

Preserved Distinction

Details

Invariant A lowering keeps every distinction a later check needs

Grounded by preserves_clause

How it is checked

Checked by the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground

Population Every test surface and document construct that names the invariant

Freshness A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes

Refusal The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause

Observation The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence

Evidence Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean

Authoritative side The invariant record, which every surface and document construct that asserts it cites

Depends on Not answered

Shape it refuses Not answered

Fresh Read

Details

Invariant A check reads a representation derived after the last relevant mutator

How it is checked

Checked by the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground

Population Every test surface and document construct that names the invariant

Freshness A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes

Refusal The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause

Observation The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence

Evidence Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean

Authoritative side The invariant record, which every surface and document construct that asserts it cites

Depends on Not answered

Shape it refuses Not answered

One Derivation

Details

Invariant One canonical question has one authoritative derivation

How it is checked

Checked by the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground

Population Every test surface and document construct that names the invariant

Freshness A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes

Refusal The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause

Observation The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence

Evidence Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean

Authoritative side The invariant record, which every surface and document construct that asserts it cites

Depends on Not answered

Shape it refuses Not answered

Weakest Link

Details

Invariant A chain is as certain as its least certain link, and a link below the floor is removed from the chain

How it is checked

Checked by the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground

Population Every test surface and document construct that names the invariant

Freshness A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes

Refusal The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause

Observation The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence

Evidence Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean

Authoritative side The invariant record, which every surface and document construct that asserts it cites

Depends on Not answered

Shape it refuses Not answered

Observation Scope

Details

Invariant Dynamic observation locates a failure and never certifies absence

How it is checked

Checked by the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground

Population Every test surface and document construct that names the invariant

Freshness A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes

Refusal The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause

Observation The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence

Evidence Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean

Authoritative side The invariant record, which every surface and document construct that asserts it cites

Depends on Not answered

Shape it refuses Not answered

Three-Condition Stop

Details

Invariant A run stops when saturation, completion and verification all hold, or when it is blocked on something outside it

How it is checked

Checked by the test surfaces that assert the invariant, through the techniques each surface lists, the structured-document validator, for each epistemic invariant the grammar's constructs ground

Population Every test surface and document construct that names the invariant

Freshness A verdict stands until the invariant, a surface that asserts it or a construct that grounds it changes

Refusal The gate fails on a surface that names an unknown invariant, and the document validator fails a gate that omits a grounded clause

Observation The runtime techniques among the surfaces that assert the invariant, which locate a violation without certifying its absence

Evidence Watched to fire and to accept: one suite plants a surface that names an unknown invariant, another plants an invariant record with no clauses, and the bundled data validates clean

Authoritative side The invariant record, which every surface and document construct that asserts it cites

Depends on Not answered

Shape it refuses Not answered

Failure shapes

Each failure shape names a way a check goes wrong without failing, the invariant it breaks, its fix, the records it shows up in and the quality rules that refuse it.

No reachable check

Details

Shape A representation that no check reaches.

Fix Declare the representation into a check's jurisdiction, or state in writing that it lies outside it.

Breaks epi-reachable-check

Seen in Manual-Only Governance, Unobservable Failure, Untested Implementation

Refused by rules None, because whether a representation is reachable is a property of the gate's jurisdiction, which no source rule sees

How it is checked

Checked by the quality rules each shape names, which refuse its syntactic signature where one exists, the classification step of the verification substrate, which files every silent failure under a shape before a fix is chosen

Population Every source file the named rules lint, and every failure a check or a review classifies

Freshness A verdict stands until the linted source, a named rule or the shape's instances change

Refusal A named rule fails the lint stage on the signature; the invariant each shape breaks is gated in every structured document that grounds it

Observation The runtime observations that locate a failure, which are then filed under a shape

Evidence Watched to fire and to accept: a suite plants a shape that names no invariant and no canon, and the bundled shapes validate clean

Authoritative side The invariant the shape breaks, which the shape cites, while each named rule conforms to the shape's signature

Depends on Not answered

Shape it refuses Not answered

Empty domain

Details

Shape A check that ran over an empty domain and reported a pass.

Fix Report the population beside every rate, and confirm at start-up that every name the check uses resolves.

Breaks epi-declared-domain

Seen in Silent Failure

Refused by rules empty-block, exception-handling

How it is checked

Checked by the quality rules each shape names, which refuse its syntactic signature where one exists, the classification step of the verification substrate, which files every silent failure under a shape before a fix is chosen

Population Every source file the named rules lint, and every failure a check or a review classifies

Freshness A verdict stands until the linted source, a named rule or the shape's instances change

Refusal A named rule fails the lint stage on the signature; the invariant each shape breaks is gated in every structured document that grounds it

Observation The runtime observations that locate a failure, which are then filed under a shape

Evidence Watched to fire and to accept: a suite plants a shape that names no invariant and no canon, and the bundled shapes validate clean

Authoritative side The invariant the shape breaks, which the shape cites, while each named rule conforms to the shape's signature

Depends on Not answered

Shape it refuses Not answered

Spent parent

Details

Shape A parent counted as read while its children were never read.

Fix Subtract the read set from the child set and report what remains.

Breaks epi-declared-domain

Refused by rules None, because a read set is known only while the run executes

How it is checked

Checked by the quality rules each shape names, which refuse its syntactic signature where one exists, the classification step of the verification substrate, which files every silent failure under a shape before a fix is chosen

Population Every source file the named rules lint, and every failure a check or a review classifies

Freshness A verdict stands until the linted source, a named rule or the shape's instances change

Refusal A named rule fails the lint stage on the signature; the invariant each shape breaks is gated in every structured document that grounds it

Observation The runtime observations that locate a failure, which are then filed under a shape

Evidence Watched to fire and to accept: a suite plants a shape that names no invariant and no canon, and the bundled shapes validate clean

Authoritative side The invariant the shape breaks, which the shape cites, while each named rule conforms to the shape's signature

Depends on Not answered

Shape it refuses Not answered

Edge from spelling

Details

Shape A dependency created because two names share a word.

Fix Join on the id the referent declares.

Breaks epi-declared-dependency

Seen in Hidden Dependency

Refused by rules None, because a join on spelling reads like any other string comparison in source

How it is checked

Checked by the quality rules each shape names, which refuse its syntactic signature where one exists, the classification step of the verification substrate, which files every silent failure under a shape before a fix is chosen

Population Every source file the named rules lint, and every failure a check or a review classifies

Freshness A verdict stands until the linted source, a named rule or the shape's instances change

Refusal A named rule fails the lint stage on the signature; the invariant each shape breaks is gated in every structured document that grounds it

Observation The runtime observations that locate a failure, which are then filed under a shape

Evidence Watched to fire and to accept: a suite plants a shape that names no invariant and no canon, and the bundled shapes validate clean

Authoritative side The invariant the shape breaks, which the shape cites, while each named rule conforms to the shape's signature

Depends on Not answered

Shape it refuses Not answered

Trusted leaf

Details

Shape A node inside the graph that is trusted without a check, such as an exit code or a modification time.

Fix Route the node through a check that can fail, and disclose what no check can reach.

Breaks epi-verdict-is-representation

Seen in Flaky Test Normalization, Mock Mirage, Security Theater

Refused by rules error-handling

How it is checked

Checked by the quality rules each shape names, which refuse its syntactic signature where one exists, the classification step of the verification substrate, which files every silent failure under a shape before a fix is chosen

Population Every source file the named rules lint, and every failure a check or a review classifies

Freshness A verdict stands until the linted source, a named rule or the shape's instances change

Refusal A named rule fails the lint stage on the signature; the invariant each shape breaks is gated in every structured document that grounds it

Observation The runtime observations that locate a failure, which are then filed under a shape

Evidence Watched to fire and to accept: a suite plants a shape that names no invariant and no canon, and the bundled shapes validate clean

Authoritative side The invariant the shape breaks, which the shape cites, while each named rule conforms to the shape's signature

Depends on Not answered

Shape it refuses Not answered

Lossy lowering

Details

Shape A reshaped representation that dropped a distinction a later check needs.

Fix Keep the distinction, and refuse at the writer anything the layout cannot express.

Breaks epi-preserved-distinction

Seen in Null Semantics Drift, Schema Drift, Silent Data Corruption

Refused by rules type-safety

How it is checked

Checked by the quality rules each shape names, which refuse its syntactic signature where one exists, the classification step of the verification substrate, which files every silent failure under a shape before a fix is chosen

Population Every source file the named rules lint, and every failure a check or a review classifies

Freshness A verdict stands until the linted source, a named rule or the shape's instances change

Refusal A named rule fails the lint stage on the signature; the invariant each shape breaks is gated in every structured document that grounds it

Observation The runtime observations that locate a failure, which are then filed under a shape

Evidence Watched to fire and to accept: a suite plants a shape that names no invariant and no canon, and the bundled shapes validate clean

Authoritative side The invariant the shape breaks, which the shape cites, while each named rule conforms to the shape's signature

Depends on Not answered

Shape it refuses Not answered

Stale read

Details

Shape A check that reads a representation the run already changed.

Fix Derive after the last mutator, and decide freshness by the fingerprint of the inputs and the code.

Breaks epi-fresh-read

Seen in Cache Poisoning by Design

Refused by rules None, because no catalogued rule refuses a cache keyed by time or by lifetime alone

How it is checked

Checked by the quality rules each shape names, which refuse its syntactic signature where one exists, the classification step of the verification substrate, which files every silent failure under a shape before a fix is chosen

Population Every source file the named rules lint, and every failure a check or a review classifies

Freshness A verdict stands until the linted source, a named rule or the shape's instances change

Refusal A named rule fails the lint stage on the signature; the invariant each shape breaks is gated in every structured document that grounds it

Observation The runtime observations that locate a failure, which are then filed under a shape

Evidence Watched to fire and to accept: a suite plants a shape that names no invariant and no canon, and the bundled shapes validate clean

Authoritative side The invariant the shape breaks, which the shape cites, while each named rule conforms to the shape's signature

Depends on Not answered

Shape it refuses Not answered

Two derivations

Details

Shape One question answered by two derivations that can drift apart.

Fix Collapse them to one derivation, computed by the producer of the answer.

Breaks epi-one-derivation

Seen in Duplicated Authority

Refused by rules duplicate-code

How it is checked

Checked by the quality rules each shape names, which refuse its syntactic signature where one exists, the classification step of the verification substrate, which files every silent failure under a shape before a fix is chosen

Population Every source file the named rules lint, and every failure a check or a review classifies

Freshness A verdict stands until the linted source, a named rule or the shape's instances change

Refusal A named rule fails the lint stage on the signature; the invariant each shape breaks is gated in every structured document that grounds it

Observation The runtime observations that locate a failure, which are then filed under a shape

Evidence Watched to fire and to accept: a suite plants a shape that names no invariant and no canon, and the bundled shapes validate clean

Authoritative side The invariant the shape breaks, which the shape cites, while each named rule conforms to the shape's signature

Depends on Not answered

Shape it refuses Not answered

Weak link kept

Details

Shape A link below the certainty floor kept in a chain with a flag on it.

Fix Remove the link from the chain.

Breaks epi-weakest-link

Refused by rules None, because the certainty of a link is a property of the chain, which no source rule sees

How it is checked

Checked by the quality rules each shape names, which refuse its syntactic signature where one exists, the classification step of the verification substrate, which files every silent failure under a shape before a fix is chosen

Population Every source file the named rules lint, and every failure a check or a review classifies

Freshness A verdict stands until the linted source, a named rule or the shape's instances change

Refusal A named rule fails the lint stage on the signature; the invariant each shape breaks is gated in every structured document that grounds it

Observation The runtime observations that locate a failure, which are then filed under a shape

Evidence Watched to fire and to accept: a suite plants a shape that names no invariant and no canon, and the bundled shapes validate clean

Authoritative side The invariant the shape breaks, which the shape cites, while each named rule conforms to the shape's signature

Depends on Not answered

Shape it refuses Not answered

Absence certified by observation

Details

Shape No observed failure read as proof that no failure exists.

Fix Use the observation to locate failures, and leave the verdict on absence to a check.

Breaks epi-observation-locates

Refused by rules None, because the shape lies in how a report is read, not in source

How it is checked

Checked by the quality rules each shape names, which refuse its syntactic signature where one exists, the classification step of the verification substrate, which files every silent failure under a shape before a fix is chosen

Population Every source file the named rules lint, and every failure a check or a review classifies

Freshness A verdict stands until the linted source, a named rule or the shape's instances change

Refusal A named rule fails the lint stage on the signature; the invariant each shape breaks is gated in every structured document that grounds it

Observation The runtime observations that locate a failure, which are then filed under a shape

Evidence Watched to fire and to accept: a suite plants a shape that names no invariant and no canon, and the bundled shapes validate clean

Authoritative side The invariant the shape breaks, which the shape cites, while each named rule conforms to the shape's signature

Depends on Not answered

Shape it refuses Not answered

Stop on confidence

Details

Shape A run that stops because the model is confident, before completion, saturation and verification hold.

Fix Stop only when the three conditions hold, or when the run is blocked on something outside it.

Breaks epi-terminate-on-three

Refused by rules None, because the shape lies in how a run decides to stop, not in source

How it is checked

Checked by the quality rules each shape names, which refuse its syntactic signature where one exists, the classification step of the verification substrate, which files every silent failure under a shape before a fix is chosen

Population Every source file the named rules lint, and every failure a check or a review classifies

Freshness A verdict stands until the linted source, a named rule or the shape's instances change

Refusal A named rule fails the lint stage on the signature; the invariant each shape breaks is gated in every structured document that grounds it

Observation The runtime observations that locate a failure, which are then filed under a shape

Evidence Watched to fire and to accept: a suite plants a shape that names no invariant and no canon, and the bundled shapes validate clean

Authoritative side The invariant the shape breaks, which the shape cites, while each named rule conforms to the shape's signature

Depends on Not answered

Shape it refuses Not answered

Unfailable floor

Details

Shape A threshold set below what its population already meets, so the check it guards cannot fail until most of the population is gone.

Fix Set the floor from the population as it stands, and plant a case below it to watch the check fail.

Breaks epi-verdict-is-representation

Refused by rules None, because whether a floor can be reached is a property of the population, which no source rule sees

How it is checked

Checked by the quality rules each shape names, which refuse its syntactic signature where one exists, the classification step of the verification substrate, which files every silent failure under a shape before a fix is chosen

Population Every source file the named rules lint, and every failure a check or a review classifies

Freshness A verdict stands until the linted source, a named rule or the shape's instances change

Refusal A named rule fails the lint stage on the signature; the invariant each shape breaks is gated in every structured document that grounds it

Observation The runtime observations that locate a failure, which are then filed under a shape

Evidence Watched to fire and to accept: a suite plants a shape that names no invariant and no canon, and the bundled shapes validate clean

Authoritative side The invariant the shape breaks, which the shape cites, while each named rule conforms to the shape's signature

Depends on Not answered

Shape it refuses Not answered

Verdictless verifier

Details

Shape A tool named as a verifier that reports no pass, no fail and no exit code, so what it examines has no check at all.

Fix Give the tool a verdict and an exit code, or rename it to the probe it is.

Breaks epi-reachable-check

Refused by rules None, because whether a tool issues a verdict is a property of its output contract, which no source rule sees

How it is checked

Checked by the quality rules each shape names, which refuse its syntactic signature where one exists, the classification step of the verification substrate, which files every silent failure under a shape before a fix is chosen

Population Every source file the named rules lint, and every failure a check or a review classifies

Freshness A verdict stands until the linted source, a named rule or the shape's instances change

Refusal A named rule fails the lint stage on the signature; the invariant each shape breaks is gated in every structured document that grounds it

Observation The runtime observations that locate a failure, which are then filed under a shape

Evidence Watched to fire and to accept: a suite plants a shape that names no invariant and no canon, and the bundled shapes validate clean

Authoritative side The invariant the shape breaks, which the shape cites, while each named rule conforms to the shape's signature

Depends on Not answered

Shape it refuses Not answered

Unindexed construct kind

Details

Shape A kind of construct the index a family of checks reads never records, so every check over that index misses every construct of the kind.

Fix Record the kind in the index, and confirm that a planted construct of the kind is reported.

Breaks epi-preserved-distinction

Refused by rules None, because an index's coverage of construct kinds is a property of its builder, which no source rule sees

How it is checked

Checked by the quality rules each shape names, which refuse its syntactic signature where one exists, the classification step of the verification substrate, which files every silent failure under a shape before a fix is chosen

Population Every source file the named rules lint, and every failure a check or a review classifies

Freshness A verdict stands until the linted source, a named rule or the shape's instances change

Refusal A named rule fails the lint stage on the signature; the invariant each shape breaks is gated in every structured document that grounds it

Observation The runtime observations that locate a failure, which are then filed under a shape

Evidence Watched to fire and to accept: a suite plants a shape that names no invariant and no canon, and the bundled shapes validate clean

Authoritative side The invariant the shape breaks, which the shape cites, while each named rule conforms to the shape's signature

Depends on Not answered

Shape it refuses Not answered

The uncovered cells

These cells of the dimension and lens grid are not yet covered by any surface. The list is derived from the grid and the surfaces, never stored.

identity through temporal

Details

identity through temporal

identity through spatial

Details

identity through spatial

identity through statistical

Details

identity through statistical

identity through frequency

Details

identity through frequency

identity through sequential

Details

identity through sequential

identity through relational

Details

identity through relational

identity through behavioral

Details

identity through behavioral

identity through functional

Details

identity through functional

identity through semantic

Details

identity through semantic

identity through causal

Details

identity through causal

identity through predictive

Details

identity through predictive

identity through anomaly

Details

identity through anomaly

identity through evolutionary

Details

identity through evolutionary

identity through fractal

Details

identity through fractal

identity through transformational

Details

identity through transformational

identity through invariant

Details

identity through invariant

identity through optimization

Details

identity through optimization

identity through complexity

Details

identity through complexity

composition through structural

Details

composition through structural

composition through temporal

Details

composition through temporal

composition through spatial

Details

composition through spatial

composition through statistical

Details

composition through statistical

composition through frequency

Details

composition through frequency

composition through sequential

Details

composition through sequential

composition through relational

Details

composition through relational

composition through functional

Details

composition through functional

composition through semantic

Details

composition through semantic

composition through causal

Details

composition through causal

composition through predictive

Details

composition through predictive

composition through anomaly

Details

composition through anomaly

composition through fractal

Details

composition through fractal

composition through transformational

Details

composition through transformational

composition through invariant

Details

composition through invariant

composition through optimization

Details

composition through optimization

composition through complexity

Details

composition through complexity

structure through temporal

Details

structure through temporal

structure through spatial

Details

structure through spatial

structure through statistical

Details

structure through statistical

structure through frequency

Details

structure through frequency

structure through sequential

Details

structure through sequential

structure through relational

Details

structure through relational

structure through behavioral

Details

structure through behavioral

structure through functional

Details

structure through functional

structure through semantic

Details

structure through semantic

structure through causal

Details

structure through causal

structure through predictive

Details

structure through predictive

structure through anomaly

Details

structure through anomaly

structure through evolutionary

Details

structure through evolutionary

structure through fractal

Details

structure through fractal

structure through transformational

Details

structure through transformational

structure through invariant

Details

structure through invariant

structure through optimization

Details

structure through optimization

structure through complexity

Details

structure through complexity

relation through structural

Details

relation through structural

relation through temporal

Details

relation through temporal

relation through spatial

Details

relation through spatial

relation through frequency

Details

relation through frequency

relation through behavioral

Details

relation through behavioral

relation through functional

Details

relation through functional

relation through semantic

Details

relation through semantic

relation through causal

Details

relation through causal

relation through predictive

Details

relation through predictive

relation through anomaly

Details

relation through anomaly

relation through evolutionary

Details

relation through evolutionary

relation through fractal

Details

relation through fractal

relation through transformational

Details

relation through transformational

relation through invariant

Details

relation through invariant

relation through optimization

Details

relation through optimization

relation through complexity

Details

relation through complexity

space through structural

Details

space through structural

space through temporal

Details

space through temporal

space through spatial

Details

space through spatial

space through statistical

Details

space through statistical

space through frequency

Details

space through frequency

space through sequential

Details

space through sequential

space through relational

Details

space through relational

space through behavioral

Details

space through behavioral

space through functional

Details

space through functional

space through semantic

Details

space through semantic

space through causal

Details

space through causal

space through predictive

Details

space through predictive

space through anomaly

Details

space through anomaly

space through evolutionary

Details

space through evolutionary

space through fractal

Details

space through fractal

space through transformational

Details

space through transformational

space through invariant

Details

space through invariant

space through optimization

Details

space through optimization

space through complexity

Details

space through complexity

time through structural

Details

time through structural

time through spatial

Details

time through spatial

time through statistical

Details

time through statistical

time through frequency

Details

time through frequency

time through sequential

Details

time through sequential

time through relational

Details

time through relational

time through behavioral

Details

time through behavioral

time through functional

Details

time through functional

time through semantic

Details

time through semantic

time through causal

Details

time through causal

time through predictive

Details

time through predictive

time through anomaly

Details

time through anomaly

time through evolutionary

Details

time through evolutionary

time through fractal

Details

time through fractal

time through transformational

Details

time through transformational

time through invariant

Details

time through invariant

time through optimization

Details

time through optimization

time through complexity

Details

time through complexity

state through temporal

Details

state through temporal

state through spatial

Details

state through spatial

state through statistical

Details

state through statistical

state through frequency

Details

state through frequency

state through relational

Details

state through relational

state through behavioral

Details

state through behavioral

state through functional

Details

state through functional

state through semantic

Details

state through semantic

state through causal

Details

state through causal

state through predictive

Details

state through predictive

state through anomaly

Details

state through anomaly

state through evolutionary

Details

state through evolutionary

state through fractal

Details

state through fractal

state through transformational

Details

state through transformational

state through invariant

Details

state through invariant

state through optimization

Details

state through optimization

state through complexity

Details

state through complexity

change through structural

Details

change through structural

change through temporal

Details

change through temporal

change through spatial

Details

change through spatial

change through statistical

Details

change through statistical

change through frequency

Details

change through frequency

change through sequential

Details

change through sequential

change through relational

Details

change through relational

change through behavioral

Details

change through behavioral

change through functional

Details

change through functional

change through semantic

Details

change through semantic

change through causal

Details

change through causal

change through predictive

Details

change through predictive

change through anomaly

Details

change through anomaly

change through evolutionary

Details

change through evolutionary

change through fractal

Details

change through fractal

change through transformational

Details

change through transformational

change through invariant

Details

change through invariant

change through optimization

Details

change through optimization

change through complexity

Details

change through complexity

behavior through structural

Details

behavior through structural

behavior through spatial

Details

behavior through spatial

behavior through statistical

Details

behavior through statistical

behavior through frequency

Details

behavior through frequency

behavior through sequential

Details

behavior through sequential

behavior through relational

Details

behavior through relational

behavior through behavioral

Details

behavior through behavioral

behavior through functional

Details

behavior through functional

behavior through semantic

Details

behavior through semantic

behavior through causal

Details

behavior through causal

behavior through predictive

Details

behavior through predictive

behavior through anomaly

Details

behavior through anomaly

behavior through evolutionary

Details

behavior through evolutionary

behavior through fractal

Details

behavior through fractal

behavior through transformational

Details

behavior through transformational

behavior through invariant

Details

behavior through invariant

behavior through optimization

Details

behavior through optimization

behavior through complexity

Details

behavior through complexity

function through structural

Details

function through structural

function through temporal

Details

function through temporal

function through spatial

Details

function through spatial

function through statistical

Details

function through statistical

function through frequency

Details

function through frequency

function through sequential

Details

function through sequential

function through relational

Details

function through relational

function through functional

Details

function through functional

function through semantic

Details

function through semantic

function through causal

Details

function through causal

function through predictive

Details

function through predictive

function through anomaly

Details

function through anomaly

function through evolutionary

Details

function through evolutionary

function through fractal

Details

function through fractal

function through transformational

Details

function through transformational

function through invariant

Details

function through invariant

function through optimization

Details

function through optimization

function through complexity

Details

function through complexity

cause through structural

Details

cause through structural

cause through temporal

Details

cause through temporal

cause through spatial

Details

cause through spatial

cause through statistical

Details

cause through statistical

cause through frequency

Details

cause through frequency

cause through sequential

Details

cause through sequential

cause through relational

Details

cause through relational

cause through behavioral

Details

cause through behavioral

cause through functional

Details

cause through functional

cause through semantic

Details

cause through semantic

cause through predictive

Details

cause through predictive

cause through anomaly

Details

cause through anomaly

cause through evolutionary

Details

cause through evolutionary

cause through fractal

Details

cause through fractal

cause through transformational

Details

cause through transformational

cause through invariant

Details

cause through invariant

cause through optimization

Details

cause through optimization

cause through complexity

Details

cause through complexity

meaning through structural

Details

meaning through structural

meaning through temporal

Details

meaning through temporal

meaning through spatial

Details

meaning through spatial

meaning through statistical

Details

meaning through statistical

meaning through sequential

Details

meaning through sequential

meaning through relational

Details

meaning through relational

meaning through behavioral

Details

meaning through behavioral

meaning through functional

Details

meaning through functional

meaning through causal

Details

meaning through causal

meaning through predictive

Details

meaning through predictive

meaning through anomaly

Details

meaning through anomaly

meaning through evolutionary

Details

meaning through evolutionary

meaning through fractal

Details

meaning through fractal

meaning through transformational

Details

meaning through transformational

meaning through invariant

Details

meaning through invariant

meaning through optimization

Details

meaning through optimization

meaning through complexity

Details

meaning through complexity

scale through structural

Details

scale through structural

scale through temporal

Details

scale through temporal

scale through spatial

Details

scale through spatial

scale through frequency

Details

scale through frequency

scale through sequential

Details

scale through sequential

scale through relational

Details

scale through relational

scale through behavioral

Details

scale through behavioral

scale through functional

Details

scale through functional

scale through semantic

Details

scale through semantic

scale through causal

Details

scale through causal

scale through predictive

Details

scale through predictive

scale through evolutionary

Details

scale through evolutionary

scale through fractal

Details

scale through fractal

scale through transformational

Details

scale through transformational

scale through invariant

Details

scale through invariant

scale through optimization

Details

scale through optimization

scale through complexity

Details

scale through complexity

probability through structural

Details

probability through structural

probability through spatial

Details

probability through spatial

probability through statistical

Details

probability through statistical

probability through frequency

Details

probability through frequency

probability through sequential

Details

probability through sequential

probability through relational

Details

probability through relational

probability through behavioral

Details

probability through behavioral

probability through functional

Details

probability through functional

probability through semantic

Details

probability through semantic

probability through causal

Details

probability through causal

probability through predictive

Details

probability through predictive

probability through evolutionary

Details

probability through evolutionary

probability through fractal

Details

probability through fractal

probability through transformational

Details

probability through transformational

probability through invariant

Details

probability through invariant

probability through optimization

Details

probability through optimization

probability through complexity

Details

probability through complexity

novelty through structural

Details

novelty through structural

novelty through temporal

Details

novelty through temporal

novelty through spatial

Details

novelty through spatial

novelty through statistical

Details

novelty through statistical

novelty through frequency

Details

novelty through frequency

novelty through sequential

Details

novelty through sequential

novelty through relational

Details

novelty through relational

novelty through behavioral

Details

novelty through behavioral

novelty through functional

Details

novelty through functional

novelty through semantic

Details

novelty through semantic

novelty through causal

Details

novelty through causal

novelty through predictive

Details

novelty through predictive

novelty through evolutionary

Details

novelty through evolutionary

novelty through fractal

Details

novelty through fractal

novelty through transformational

Details

novelty through transformational

novelty through invariant

Details

novelty through invariant

novelty through optimization

Details

novelty through optimization

novelty through complexity

Details

novelty through complexity

The maps

The reasoning collection carries these maps beside its records, namely the foundation sequence with the math types on each of its layers, the invariant groups, and the operations a pattern admits.

Foundation sequence

Details

logic-set-theory-axioms β†’ structure β†’ change β†’ relationships β†’ possibility β†’ application

structure

Details

algebra, geometry

change

Details

analysis, dynamics

relationships

Details

category-theory, information-theory

possibility

Details

probability, computation, complexity

generative

Details

objects, relations, transformations, constraints, emergence

systemic

Details

entity, relation, state, transformation, constraint, information, feedback, emergence

Members

Details

detection, classification, explanation, prediction, generation

The groundings

Every grounding edge the reasoning collection declares is listed with the record it leaves from and the record or grammar it lands on, or with the label it carries where it names a rule rather than a record.

ver-evidence

Details

ver-evidence β†’ Carries: an unverified claim carries no weight

constrain

Details

constrain β†’ Lands on: Governed Autonomous Plan Loop

derivation-loop

Details

derivation-loop β†’ Lands on: Checklist Creation Kernel

derivation-loop

Details

derivation-loop β†’ Lands on: checklist

Algorithms Β· Grammar