Repository navigation
packages ui
Scope. Root primitive used by golden-path. Product UIs (SentraBot, Kediri, Smartboard, portfolio) do not consume this package.
React primitives built on the Sentra design tokens. Deliberately minimal — one exported component (StatusCard). Shared-package changes are R2.
| File | Purpose |
|---|---|
packages/ui/src/index.ts |
Barrel: exports StatusCard + StatusCardState
|
packages/ui/src/status-card.tsx |
The StatusCard component |
packages/ui/package.json |
Depends on @sentra/token; react is a peer dependency |
StatusCard (packages/ui/src/status-card.tsx) renders a labelled status panel with an inline state badge:
- Props:
label,detail,state("ready" | "attention"), and optionalchildren. - Renders an
<article class="status-card" data-state={state}>with a heading, the label, a short detail paragraph, and any children. - The visible state text is localised (Bahasa Indonesia):
ready→ "Siap",attention→ "Perlu perhatian".
Styling is class-driven (status-card, status-card__*) so the actual colours come from @sentra/token (see Token); the component carries no raw colour or radius values, which keeps it inside the governance token gate.
import { StatusCard } from "@safrs/ui";
<StatusCard
label="Database"
detail="Local disposable database is ready."
state="ready"
/>-
@safrs/webconsumes@safrs/ui(declared inprojects/internal/golden-path/apps/web/package.json). -
@sentra/tokenprovides the design tokens the component styles against;check-tokens.mjsenforces that no raw values leak into this package.
pnpm --filter @safrs/ui lint
pnpm --filter @safrs/ui typecheck
pnpm --filter @safrs/ui test
pnpm --filter @safrs/ui build- Token — mandatory design tokens for all UI work
- UI rules — the full UI conventions this component follows
- Shared 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
- 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