Writing index
Program update
October 6, 2026
11 min read

Current Technical Program

SentinelOps is building a verification stack around one operational question. Which evidence supports the release of a consequential effect? The program joins action policy, permission state, runtime mediation, evidence identity, replay, and conformance testing into one inspectable execution record.

01 · Runtime control

Compile governed actions into executable monitors

Action-level specifications define admissible traces over a labeled event alphabet. Compilation produces deterministic monitors plus artifacts that document the relation between the source policy and the executable transition system. Runtime mediation places those monitors on the effect path.

The evaluation target is semantic agreement. Reference semantics and deployed verdicts need to match across representative traces and adversarial traces. Monitor cost is reported separately from semantic correctness.

02 · Permission state

Use one authorization model across tools and data

Calls and data operations reference the same permission state. Attribute-based rules and relationship-based rules feed one decision record. Permission epochs fix the state snapshot associated with a decision and give revocation a defined transition model.

Field-level decisions use compact witnesses where the policy model supports them. The evidence record identifies the witness scheme and verification result, keeping the authorization claim separate from the runtime policy claim.

03 · Evidence record

Bind every verdict to the artifacts that define its meaning

The certificate schema records policy identity and monitor identity. It also records permission state and verdict data. Relevant proof artifacts are referenced separately. Signatures protect artifact identity. Supply-chain provenance documents the software build associated with the runtime record.

Record fieldPurposeIndependent check
Policy hashNames the governing specificationHash comparison
Monitor hashNames executable semanticsArtifact verification
Permission stateNames the authorization snapshotState reconstruction
VerdictRecords the release decisionReference replay
04 · Replay

Make incident reconstruction a first-class output

Replay bundles record the execution fragment needed to reconstruct a selected decision under a declared profile. Egress normalization reduces variation caused by chunking and environment settings. The replay record also identifies state external to the bundle.

Independent reconstruction tests focus on verdict agreement and trace agreement. Divergence is classified as an engineering defect or as a stated profile limitation.

05 · Conformance

Test the deployed runtime against a reference semantics

Conformance work uses curated traces and adversarial generators. The test record compares source policy, reference decision, deployed decision, evidence record, and replay result. Counterexamples are reduced to the smallest trace that preserves the disagreement where practical.

This programme provides implementation teams with a direct engineering target. It also provides external evaluators with a stable basis for examining changes across runtime versions.

06 · Near-term outputs

Publish testable interfaces for external teams

Near-term work centers on certificate schema definition, deterministic replay profiles, unified permission semantics, and local-to-global information-flow statements. Each public interface is paired with a reference implementation or verifier plus conformance material.

The programme treats public evidence as part of the technical output. Documentation establishes the public interface. Reference traces provide test inputs. Implementation hashes identify artifacts. Evaluation records provide external teams with material for direct claim testing.