Repository navigation
overview getting started
There are two entry points. Pick the one that matches the work.
Use this for governance tooling, golden-path demo, or control-center.
- Node.js
>= 24.18 < 25 - pnpm 11.21.0 (
packageManagerfield;corepack enableif needed) - Docker Desktop (root Postgres on
127.0.0.1:54329) - Python 3 (
safrs-verify) - Git LFS (Playwright visual baselines)
pnpm install
pnpm run setuppnpm run setup runs scripts/setup.mjs: environment checks, Docker Postgres, Prisma generate/migrate/seed for the root @safrs/database demo.
pnpm doctor # environment diagnosis
pnpm status # task registry and leases
pnpm dev # golden-path Next.js (scripts/dev.mjs)
pnpm test # contract + unit tests
pnpm test:e2e # Playwright
pnpm check # governance + tokens + lint + typecheck + test + build
pnpm governance # SAFRS local verificationpnpm task claim --id TASK-YYYYMMDD-XXX --title "..." --owner-id <id> --owner-label "<agent>" --risk R1 --scope <path>
pnpm task state --id TASK-YYYYMMDD-XXX --to EXECUTING
pnpm task list --active
pnpm task close --id TASK-YYYYMMDD-XXXRegistry files live under the git common directory (.git/safrs-control-plane/), not in the working tree.
pnpm db:start
pnpm db:migrate
pnpm db:seed
pnpm db:studio
pnpm db:reset # blocked unless disposable (reset guard)Postgres image: postgres:17-alpine in root compose.yaml. This is not Kediri's or SentraBot's database.
Work from the capsule root. Do not use root pnpm --filter as the lifecycle.
cd projects/product/sentrabot # example
# then the capsule's own install / test / build from project.contract.json
pnpm project:status # from repo root: list contracts
pnpm project:verify product/kediri-historyStandalone proof: tools/project-standalone copies the capsule out of the monorepo and runs declared lifecycle commands. See Standalone verification.
Read the capsule AGENTS.md before changing it. Product docs beat this wiki for runtime detail.
| Capsule | Capsule docs |
|---|---|
| SentraBot | projects/product/sentrabot/docs/architecture.md |
| Kediri | projects/product/kediri-history/README.md |
| Avery | projects/healthcare/avery/docs/spds/read_first.md |
| Smartboard | projects/academic/academic-smartboard/docs/architecture.md |
| Portfolio | projects/corporate/portfolio-drnovia/docs/quickstart.md |
docker compose -f compose.telemetry.yaml up -d jaeger
# UI http://localhost:16686 OTLP http://localhost:4318/v1/traces- Do not
git clean -xdfat repo root — it deletes gitignoreddatabase/corpus data. - Do not read, print, or commit
.envor production credentials. - Do not push without Chief's explicit session order (
CHIEF_PUSH_OK; project paths needCHIEF_PUSH_PROJECTS_OK). See.agents/BOUNDARIES.md. - Do not copy golden-path's
@safrs/*imports into a new capsule.
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