Pre-execution policy evaluation
Entity, operator, environment, tool, and action are checked against authority policy.
OPERATING-SYSTEM MODEL
Architecture
Fenrua is organized as kernel space and user space, with stable machine-readable interfaces and public evidence boundaries.
CONTROL FLOW
Security workflow
USERS, OPERATORS, ORGANISATIONS
AI APPLICATIONS AND WORKFLOWS
AGENTS, MODELS, TOOLS, ORCHESTRATORS
COMPUTE, DATA, APIS, CLOUD, CHAINS
FENRUA USER-SPACE INTEGRATIONS
FENRUA SECURITY KERNEL
IDENTITY · AUTHORITY · INTEGRITY · POLICY · EVIDENCE · VERIFICATION · CONTAINMENT · RECOVERY
Tool-call authorization
Allowed, denied, scoped, and human-approval actions are explicit.
Runtime-integrity verification
Source, build, lockfile, image, model, policy, and deployment manifests are compared.
Evidence-bundle creation
Inputs, outputs, decisions, commands, findings, hashes, and limitations become records.
Revocation and quarantine
Invalid, stale, drifted, revoked, or incomplete evidence fails closed.
Research-to-kernel translation
Research observations are promoted only through claims, non-claims, tests, evidence, utilities, and regressions.
VIEWPOINTS
Inspect the boundary from each relevant angle
These routes use semantic diagrams and explicit state labels. They distinguish current public records, reference designs, specifications, research, planned work, agreement-specific delivery, and external dependencies.
System context
This view separates the public evidence interface, local technical work, agreement-specific services, and external systems. It is a scope map, not a deployment inventory.
Open viewpointLogical components
Logical components are presented as distinct evidence, policy, verification, and recovery responsibilities. A component label does not establish a deployed service.
Open viewpointRuntime sequence
The reference sequence explains how a local workflow can evaluate supplied artifacts. It describes a design boundary, not a live multi-tenant runtime.
Open viewpointDeployment profiles
The complete reference profile is chain-free and local-first. Optional signed observations are publication or ordering inputs only; they do not create authorization or prove deployment correctness.
Open viewpointTrust boundaries
Trust is scoped to named artifacts, signatures, policies, public records, and review boundaries. The page never collapses a signed observation into general system assurance.
Open viewpointData and provenance
This view distinguishes public static records, bounded observation fields, agreement-specific information, and protected operational material. Public evidence is point-in-time and limitation-aware.
Open viewpointRecovery and containment
Failure handling is designed around explicit invalid, stale, revoked, incomplete, or superseded states. The site publishes the decision boundary, not an invented incident history.
Open viewpointEvolution states
Every major surface is labelled by its actual state so that public documentation cannot be mistaken for a production capability roadmap.
Open viewpoint