Policy and governance
Policies, objectives, approvals and the decisions that set them.
Observation framework for regulated systems
Regulated systems answer to standards: ISO management systems, prudential standards, codes of practice and best-practice guides. selfdriven.observer turns a standard into criteria that octonomous systems watch every day. Human observers hold the judgement and the signature.
steps from a standard's requirement to an assurer's reading of the record
octonomous observers, one for each selfdriven Area of Focus
of the population observed, where an audit tested a sample
human signature on every finding before it reaches the record
The framework
Clauses, controls, paragraphs, strategies: the vocabulary changes and the structure stays. A standard states requirements. An organisation decides what meeting them looks like. Evidence shows whether it does. The framework makes each step observable and signs it.
What the standard asks, referenced by its own identifier. The framework holds references, never the standard's text.
What meeting the requirement looks like here, with a threshold, a population and a cadence.
Where the truth already lives: the system, log or record that shows whether the criterion holds.
The criterion tested against the whole population and signed by the observer that ran it.
Conforming, opportunity for improvement or nonconformity. A human observer confirms the grade and signs.
The certification body, regulator or assessor reads the record for the period they assure.
What the framework is made of
Only the profile changes between standards. Scope, criteria, observers, connectors, the record and its views work the same way for every standard you load.
The standard as structured data: identifiers, units of requirement, applicability rules and relationships to other standards. Licensed text stays with its publisher.
profileThe system being observed and which requirements apply to it, with the reason for each exclusion.
scope · applicabilityYour own tests for each requirement: what is measured, across which population, against what threshold, how often.
criterionEight octonomous observers, each delegated by a human conductor, plus the human observers who review their findings.
observer AIDRead-only links to the systems that already hold the evidence: cloud accounts, identity, ticketing, HR, finance, operations.
connectorEvery observation, finding and review as a verifiable credential, anchored in the signer's key event log.
ACDC · KELThe record cut for each reader: operators, management, the board, auditors and regulators.
viewStandards it fits
If a standard states requirements and evidence can show they are met, it fits the framework. ISO/IEC 27001 is the first profile. The rest show the range of standards with the same shape.
Clauses plus controls. Assured by accredited certification bodies.
Numbered obligations. Supervised by a regulator, owned by the board.
Functions, strategies and maturity levels. Self-assessed or independently assessed.
Criteria tested over a period. Reported on by an independent firm or assessor.
Human tools & octonomous systems
Two kinds of observer work side by side under every standard. Octonomous systems read, test and report without pause. Human observers hold the conversations, the judgement and the signature, using tools built around the record.
For the human observer, the system owner and the assurer who reads the record.
Eight observers organised on the selfdriven Areas of Focus, each conducted by a human.
Each observer watches one Area of Focus, whichever standard is loaded.
Policies, objectives, approvals and the decisions that set them.
Suppliers, cloud providers, customers and regulators.
Training, onboarding and the competence each role requires.
Identity, access, cryptography and data standards.
Continuity, capacity, backup and the resources behind them.
Operations, change, configuration and service delivery.
Logs, monitoring, incidents, internal audit and reporting.
Roles, segregation of duties, joiners, movers and leavers.
What the human auditor used to do
Assurance has run on visits: a few days on site, a sample tested, a report written, then a year of quiet. The framework keeps the same questions open every day and leaves the judgement with people.
The auditor tested 25 of 400 access reviews. Observers test all 400, every time one changes.
Assurance arrived once a year. Observation runs every day, and the assurer reads any period they choose.
Evidence was a file someone saved. Now each result is a credential anyone can verify.
Use cases
The framework with the ISO/IEC 27001:2022 profile loaded. All 93 Annex A controls mapped to the eight observers, a three-year certification cycle observed every day, and a signed record ready for the certification body.
The next profiles are chosen with the organisations that bring them. Bring a standard.
Assurance
The framework doesn't certify, attest or supervise. Certification bodies, regulators and assessors keep that role. They get a continuous, signed record to work from in place of evidence gathered the week before.
Observations are ACDC credentials chained to the requirement, the observer and the reviewer. An assurer checks the signatures against the key event logs, not against our word.
Every observer AID is delegated from a human conductor's AID with a dip event. If an observer misbehaves, its conductor revokes it and the record shows when.
Assurer access is a credential for a defined window. It opens the record for that period and expires on its own.