Repository navigation
lore
The SAFRS Monorepo was bootstrapped in August 2026 by Dr. Ferdi Iskandar (Chief) and then expanded from a single golden-path demo into a control plane over sovereign capsules.
This page is historical narrative. It is not architecture truth. ADRs and MONOREPO_PURPOSE.md win.
SAFRS v1.1 skeleton: six-layer control architecture, policy.json, R0–R3, agent roles, sensitive paths. Topology decision: projects / packages / tools / tests / docs.
ADR 0001 chose one Next.js app mounting a package-owned Hono API under /api, Zod as the shared contract.
.agents/ memory files and registry-driven routing. Vendor adapters for Claude, Cursor, Codex. @sentra/design-tokens renamed to @sentra/token. Email and Stripe capability packs activated. Docs converted to concise English.
Telemetry, codegen, deps-graph, OpenAPI endpoint, property tests, supply-chain scan. Corpus-engine PoC for medical PDFs (data still lives gitignored in root database/).
ADR 0002: canonical JSON contracts, monotonic risk, leases, PR gates, evidence, publisher identity.
ADR 0005: every capsule at projects/<domain>/<capsule>/.
ADR 0006: root is optional; extraction is proof.
Smartboard migrated from abyss-monorepo (ADR 0003). SentraBot public-release decision (ADR 0004).
-
2026-08-25: origin
mainrewritten (5b6b808); local history is unrelated. Push/fetch requires the filtered publish flow (.agents/BOUNDARIES.md). - 2026-08-26: Kediri capsule: Payload, GSAP journey, Docker Postgres + MinIO, standalone verify PASS.
- 2026-09-03: SentraBot excluded from the root pnpm workspace as its own lockfile.
-
2026-09-02: SentraBot architecture doc frozen against code (
apps/apiis the harness on port 3100).
-
2026-09-10: Wiki refreshed to the control-plane + capsule topology (the
sentrawiki/baseline this page supersedes). - 2026-09-13 … 09-15: Academic Smartboard web ported through sub-phase 5 — scheduling, academics, evaluasi, payroll/overtime, ops/master data, then admin + Kayyisa (pengaturan, persetujuan, platform, Kayyisa trajectory panel).
-
2026-09-19 … 09-21: Gaffer orchestration lands in three phases — Ports Wiring (
tools/automation/src/gaffer/safrs-ports.mjs), Provider Activation (provider-codex.mjs+pnpm saf gaffer run), and the accompanying architecture handoff (docs/architecture/GAFFER_ORCHESTRATION_FRAMEWORK.md). The current Codex provider callbacks are simulated and its default audit returnsSHIPwithout independent review; Phase 4 economic validation is still open.
- Typed demo flow (ADR 0001) still exists as the legacy golden-path.
- Zod contracts for that demo.
- Database reset guard for disposable local Postgres.
- Human-Governed · Agent-Executed · Machine-Enforced.
- Sentra-GSAP QA gates withdrawn 2026-08-28; motion uses official GSAP skills. Historical FAIL on those gates is not a current gate.
- Root-coupled capsules as a pattern — still present as defects, forbidden as templates.
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