Repository navigation
verification standalone
Canonical: ADR 0006, docs/governance/CAPSULE_SOVEREIGNTY.md.
Tool: tools/project-standalone (pnpm project:status, pnpm project:verify <domain/capsule>).
Empirical extraction is decisive:
- Copy only the capsule to a fresh directory outside the Monorepo.
- Deny access to the root.
- Install using capsule-owned lock state.
- Run declared lint/typecheck when applicable.
- Run tests, build, disposable run, smoke, deploy dry-run.
- Confirm no required path resolved outside the extracted capsule.
HANDOFF (2026-08-26) records project-standalone verify product/kediri-history PASS after a Docker Postgres 18.6 + MinIO empty-database run.
Trap recorded in Kediri docs/testing.md: next build does not clear .next/dev/; leftover pnpm dev symlinks fail standalone verify. Remove apps/web/.next before verify.
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