Repository navigation
packages
Canonical: packages/README.md. Changes are R2.
Root packages/ holds reusable, product-neutral capabilities. They are not the runtime dependency pattern for new capsules (ADR 0006). Standalone capsules must not resolve these after extraction.
Allowed consumers today: the legacy golden-path app, and (narrowly) control-center for @sentra/token / @safrs/config. Those couplings are current-state defects or operator-surface exceptions, not templates.
| Package | Directory | Role |
|---|---|---|
@safrs/config |
packages/config/ |
Shared tsconfig presets |
@safrs/schemas |
packages/schemas/ |
Zod demo contracts (barrel); src/sentrabot/ not exported |
@safrs/env |
packages/env/ |
t3-env client/server split |
@safrs/telemetry |
packages/telemetry/ |
OpenTelemetry + Hono middleware |
@sentra/token |
packages/token/ |
Sentra design tokens (authoring source) |
@safrs/ui |
packages/ui/ |
StatusCard primitive |
@safrs/database |
packages/database/ |
Prisma + Postgres, reset guard, seed |
@safrs/api |
packages/api/ |
Hono routes, typed client, OpenAPI |
| (incomplete) | packages/auth/ |
Better Auth sources without a shipped package.json — auth.md |
packages/auth/src exists with Better Auth + Prisma adapter in node_modules, but there is no published workspace package.json in the listing used for this wiki. Do not treat @safrs/auth as a shipped package.
graph TD
CONFIG["@safrs/config"]
SCHEMAS["@safrs/schemas"]
ENV["@safrs/env"]
TELE["@safrs/telemetry"]
TOKEN["@sentra/token"]
DB["@safrs/database"]
UI["@safrs/ui"]
API["@safrs/api"]
WEB["@safrs/web golden-path"]
DB --> ENV
DB --> TELE
UI --> TOKEN
API --> DB
API --> SCHEMAS
API --> TELE
WEB --> API
WEB --> DB
WEB --> ENV
WEB --> TELE
WEB --> UI
WEB --> TOKEN
SentraBot, Kediri, and Smartboard keep capsule-local packages (@sentrabot/*, @kediri/*, vendored token tarball). Those are not these packages.
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