Repository navigation
overview conformance
Canonical: SAFRS_SPEC.md §19 and docs/governance/safrs_conformance.md.
| Level | Meaning |
|---|---|
| SAFRS Core | Canonical routing, policy, risk tiers, local verification |
| SAFRS Controlled | Core + CI enforcement + sensitive-path gates + review rules |
| SAFRS Secure | Controlled + execution isolation + credential/network controls + supply-chain protections |
| SAFRS Regulated | Secure + auditable approvals, domain-specific invariants, controlled production access, evidence retention |
SAFRS Core (assessment date 2026-08-10 in docs/governance/safrs_conformance.md).
Core is achieved because routing, R0–R3 policy, sensitive-path declaration, document registry, topology checks, tool inventory, and local safrs-verify exist.
Controlled is not claimed. CI workflows are committed, but required branch protection / CODEOWNERS enforcement on the remote is not proven. HANDOFF (2026-08-26) records GitHub Free private-repo branch-protection limits.
Secure is not claimed.
Regulated is not claimed and must not be inferred from the presence of a healthcare/ domain folder. Healthcare-domain capsules still have to classify clinical overclaim (see Avery SPDS). A domain name is not a medical-device claim.
SAFRS — the Sentra Agent-First Repository Standard — defines how a software repository should be structured, governed, and enforced when autonomous Artificial Intelligence agents perform a substantial share of engineering work by Sentra Artificial Intelligence.
SAFRS v1.1 addresses that problem through five coupled mechanisms:
- a six-layer repository architecture from Trust Boundary to Human Authority;
- a role-based permission model in which capability never implies trust;
- a four-tier risk model with cumulative mandatory controls;
- a multi-agent execution protocol with explicit task states and one mutation owner per bounded scope;
- a knowledge governance model that distinguishes current architecture, historical decisions, execution plans, Git history, and running code.
Built in Indonesia as part of the Sentra Artificial Intelligence ecosystem.
Sentra Artificial Intelligence · Source Repository · Official Website
Dr Ferdi Iskandar — Creator & Maintainer
LinkedIn ·
ORCID ·
Hugging Face ·
Kaggle ·
Medium ·
Substack ·
X ·
Threads
MyPrompt · Sentra Artificial Intelligence · Indonesia
- SentraBot
- Kediri History
- Academic Smartboard
- Avery
- Portfolio Dr. Novia
- Golden Path (legacy demonstrator)
- Control Center
- Capsule template
- Risk model (R0–R3)
- Agent roles and permissions
- Capsule sovereignty
- Multi-agent protocol
- Document lifecycle
- Sensitive paths
- Verification integrity
Lore — how this repository grew
- Schemas (
@safrs/schemas) - Environment (
@safrs/env) - Database (
@safrs/database) - API (
@safrs/api) - UI (
@safrs/ui) - Telemetry (
@safrs/telemetry) - Token (
@sentra/token) - Config (
@safrs/config) - Auth (
packages/auth)
- SAFRS governance checkers
- SAFRS Automation Control Plane
- Gaffer Runtime
- Doctor
- Project wizard
- project-standalone
- Capabilities
- Codegen
- Deps-graph
- Status CLI
- Task CLI