Repository navigation
packages config
Scope. tsconfig presets for root workspace members (
packages/*,tools/*, includedprojects/*/*/apps/*). Excluded capsules (SentraBot, Kediri, Smartboard) ship their own tsconfig.
Shared TypeScript presets so root-workspace packages get identical strict compiler settings. Two presets; consumed as a dev dependency by those packages' typecheck scripts.
| File | Purpose |
|---|---|
packages/config/package.json |
Exports ./tsconfig/base.json and ./tsconfig/nextjs.json
|
packages/config/tsconfig/base.json |
The strict baseline preset |
packages/config/tsconfig/nextjs.json |
Next.js preset extending the baseline |
packages/config/tsconfig/base.json enforces the monorepo's strict baseline:
target: ES2024-
module: NodeNext,moduleResolution: NodeNext strict: truenoEmit: trueskipLibCheck: trueverbatimModuleSyntax: true
packages/config/tsconfig/nextjs.json extends the baseline for Next.js surfaces:
lib: ["DOM", "DOM.Iterable", "ES2024"]jsx: "preserve"- the
nextTypeScript plugin
// tsconfig.json (workspace member)
{
"extends": "@safrs/config/tsconfig/base.json"
}- Every
packages/*package lists@safrs/configas a dev dependency and runstsc --project tsconfig.jsonfortypecheck. -
projects/internal/golden-path/apps/webuses@safrs/config/tsconfig/nextjs.jsonfor its App Router surface.
pnpm --filter @safrs/config lint
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
- SentraBot
- Kediri History
- Academic Smartboard
- Avery
- Portfolio Dr. Novia
- Golden Path (legacy demonstrator)
- Control Center
- Capsule template
- Risk model (R0–R3)
- Agent roles and permissions
- Capsule sovereignty
- Multi-agent protocol
- Document lifecycle
- Sensitive paths
- Verification integrity
Lore — how this repository grew
- Schemas (
@safrs/schemas) - Environment (
@safrs/env) - Database (
@safrs/database) - API (
@safrs/api) - UI (
@safrs/ui) - Telemetry (
@safrs/telemetry) - Token (
@sentra/token) - Config (
@safrs/config) - Auth (
packages/auth)
- SAFRS governance checkers
- SAFRS Automation Control Plane
- Gaffer Runtime
- Doctor
- Project wizard
- project-standalone
- Capabilities
- Codegen
- Deps-graph
- Status CLI
- Task CLI