Repository navigation
background
Canonical records: docs/adrs/ and .agents/DECISIONS.md. This page is a pointer.
ADR 0001 needed an executable typed Database → API → Web journey without inventing a product domain. That app still exists. It is no longer the shape of new work.
ADR 0002 put contracts, risk, leases, and evidence in-repo instead of a custom service.
ADR 0005 groups products by compliance context. Domain folders own no code.
ADR 0006 rejected "root-managed runtime for every capsule" and "one repo per project with no control plane".
Selective copy, never lift-and-shift (decision 2026-08-11). .env from the old tree is never read. Lessons: .agents/knowledge/12_LESSONS.md.
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