 dr codieverse · Personal Website |
This repository is designed as the personal website and public founder dossier of Dr. Ferdi Iskandar — a structured digital home for identity, work, writing, speaking profile, selected systems, public credibility surfaces, and AI-assisted visitor guidance. Purpose To present Dr. Ferdi Iskandar's public identity with clarity, credibility, and institutional tone. To organize professional background, founder journey, leadership work, healthcare AI initiatives, and public-facing projects. To provide a navigable founder dossier for partners, media, event organizers, collaborators, healthcare leaders, and technology communities. To support AI-augmented public profile exploration through Abby, while preserving safe boundaries, controlled knowledge, and editorial consistency. Founder, Sentra Artificial Intelligence |
Sentra Founder Dossier is not a generic personal portfolio. It is a structured public-profile infrastructure for presenting the identity, work, credibility, writing, systems, speaking surface, and collaboration pathways of dr Ferdi Iskandar.
The repository exists to make the founder's public presence:
- clearer for media, partners, event organizers, and institutional visitors;
- easier to navigate through route-based editorial surfaces;
- safer to ask about through a bounded AI assistant named Abby;
- consistent with the Sentra ecosystem's design principle: clarity first, intelligence second, decoration last.
A founder website should not merely display information. It should reduce ambiguity, build trust, and guide the visitor toward the right next action.
|
A publication-grade personal website for explaining identity, leadership history, work domains, public credibility, and collaboration routes. |
A controlled public assistant that helps visitors understand the founder, the website, selected work, speaking context, and collaboration pathways. |
A Next.js application with curated routes, AI provider abstraction, Markdown knowledge files, safety boundaries, metadata, verification commands, and deployment discipline. |
This README uses a more visual Sentra-style documentation layer: structured, institutional, warm, colorful, and system-oriented.
| Design principle | Application in this README |
|---|---|
| Hero-first clarity | The repository identity is visible immediately at the top. |
| Diagram-rich explanation | Architecture, flow, boundaries, and verification are visualized with Mermaid. |
| Color-coded domains | Public routes, AI layers, knowledge, security, and deployment use distinct colors. |
| Executive readability | Sections are written for fast scanning by founder, engineer, auditor, or collaborator. |
| No noisy decoration | Colors support structure; they do not replace substance. |
flowchart LR
Founder["dr Ferdi Iskandar<br/>Founder Identity"]
Site["Founder Dossier Site<br/>Public Routes"]
Abby["Abby AI Assistant<br/>Guided Conversation"]
Knowledge["Controlled Knowledge Base<br/>content/abby/*.md"]
APIs["Next.js API Routes<br/>/api/abby + /api/chat"]
Providers["AI Provider Layer<br/>Gemini + DeepSeek + OpenAI + NVIDIA Legacy"]
Visitor["Public Visitor<br/>Media · Partner · Event Organizer"]
Action["Visitor Action<br/>Read · Ask · Contact · Collaborate"]
Founder --> Site
Site --> Visitor
Visitor --> Abby
Abby --> APIs
APIs --> Knowledge
APIs --> Providers
Knowledge --> Abby
Abby --> Action
Site --> Action
classDef founder fill:#FFF7ED,stroke:#F97316,color:#7C2D12,stroke-width:2px;
classDef site fill:#EFF6FF,stroke:#2563EB,color:#1E3A8A,stroke-width:2px;
classDef ai fill:#FDF2F8,stroke:#DB2777,color:#831843,stroke-width:2px;
classDef knowledge fill:#ECFDF5,stroke:#10B981,color:#064E3B,stroke-width:2px;
classDef api fill:#F5F3FF,stroke:#7C3AED,color:#312E81,stroke-width:2px;
classDef visitor fill:#FEFCE8,stroke:#CA8A04,color:#713F12,stroke-width:2px;
classDef action fill:#F0FDFA,stroke:#14B8A6,color:#134E4A,stroke-width:2px;
class Founder founder;
class Site site;
class Abby ai;
class Knowledge knowledge;
class APIs,Providers api;
class Visitor visitor;
class Action action;
The application is organized as a route-based founder dossier. Every public route has a job. Nothing should exist only because it looks impressive.
| Surface | Route | Primary function | Audience |
|---|---|---|---|
| Editorial Homepage | / |
Introduce the founder, authority, work domains, and route hierarchy. | All visitors |
| About | /about |
Explain biography, professional transition, leadership background, and founder identity. | Partners, media, collaborators |
| Works | /works |
Present selected systems, projects, and initiatives connected to healthcare and AI. | Technical and institutional visitors |
| Notes | /notes |
Publish thinking, essays, reflections, and conceptual updates. | Readers, collaborators, public audience |
| Kisah Sentra | /kisah-sentra |
Tell the founding story of Sentra as an editorial narrative. | Readers, collaborators, public audience |
| Tanpa Naskah | /tanpa-naskah |
Collect unscripted quotes and reflections from the founder, grouped by theme. | Readers, collaborators, public audience |
| Human – AI Collab | /bagaimana-sentra-dibangun |
Document the dr Ferdi × Voss brainstorming session behind Sentra's clinical architecture. | Readers, technical and institutional visitors |
| Speaking | /speaking |
Support event evaluation, speaker invitation, and public-stage positioning. | Event organizers, institutions |
| CV | /cv |
Present credentials, leadership roles, medical background, and public authority. | Formal reviewers, partners |
| Abby Widget | Client overlay | Guide visitors conversationally through public profile and website context. | Visitors who prefer asking instead of browsing |
| Abby API | /api/abby |
Main AI conversation endpoint with provider abstraction and safety boundaries. | Application runtime |
| Legacy Chat API | /api/chat |
Secondary NVIDIA-based chat path retained for legacy experimentation. | Maintainers only |
flowchart TD
Home["/ <br/>Editorial Homepage"]
About["/about <br/>Founder Profile"]
Works["/works <br/>Selected Systems"]
Notes["/notes <br/>Writing Surface"]
KisahSentra["/kisah-sentra <br/>Founding Story"]
TanpaNaskah["/tanpa-naskah <br/>Unscripted Reflections"]
HumanAI["/bagaimana-sentra-dibangun <br/>Human – AI Collab"]
Speaking["/speaking <br/>Stage Profile"]
CV["/cv <br/>Credentials"]
Abby["Abby Widget <br/>Conversation Overlay"]
Contact["Future /contact <br/>Collaboration Surface"]
Systems["Future /systems <br/>Systems Catalogue"]
Home --> About
Home --> Works
Home --> Notes
Home --> KisahSentra
Home --> TanpaNaskah
Home --> HumanAI
Home --> Speaking
Home --> CV
Abby --> About
Abby --> Works
Abby --> Speaking
Abby --> Contact
Works --> Systems
Speaking --> Contact
classDef home fill:#DBEAFE,stroke:#2563EB,color:#1E3A8A,stroke-width:2px;
classDef profile fill:#FFEDD5,stroke:#F97316,color:#7C2D12,stroke-width:2px;
classDef work fill:#DCFCE7,stroke:#16A34A,color:#14532D,stroke-width:2px;
classDef writing fill:#FCE7F3,stroke:#DB2777,color:#831843,stroke-width:2px;
classDef public fill:#FEF9C3,stroke:#CA8A04,color:#713F12,stroke-width:2px;
classDef ai fill:#EDE9FE,stroke:#7C3AED,color:#312E81,stroke-width:2px;
classDef future fill:#F1F5F9,stroke:#64748B,color:#334155,stroke-dasharray: 5 5,stroke-width:2px;
class Home home;
class About,CV profile;
class Works,Systems work;
class Notes,KisahSentra,TanpaNaskah,HumanAI writing;
class Speaking public;
class Abby ai;
class Contact future;
Abby is the personal AI assistant for the public website. Abby is designed to help visitors understand public information, not to create new private claims or act as a clinical system.
| Field | Value |
|---|---|
| Name | Abby |
| Role | Personal AI assistant for dr Ferdi Iskandar |
| Primary endpoint | /api/abby |
| Default language | Bahasa Indonesia |
| Primary knowledge source | content/abby/*.md |
| System prompt | src/prompts/abby.system-prompt.md |
| Default provider | Gemini |
| Alternate provider | DeepSeek, OpenAI |
| Legacy provider | NVIDIA through /api/chat |
Abby should answer from controlled context, route visitors to the right public surface, and preserve safe scope at all times.
sequenceDiagram
autonumber
participant V as Public Visitor
participant W as Abby Widget
participant A as /api/abby
participant R as Request Validator
participant K as Knowledge Loader
participant P as System Prompt
participant M as AI Provider
participant S as Safe Response Mapper
V->>W: Ask about founder, work, route, or collaboration
W->>A: POST message + visitorMode + history
A->>R: Validate message length and payload shape
R->>K: Load public Markdown knowledge
K->>P: Merge knowledge with behavior rules
P->>M: Send bounded prompt to selected provider
M->>S: Return model output
S->>A: Normalize plain-text reply
A->>W: Return safe public answer
W->>V: Display Abby guidance
flowchart TB
Config["src/config/*.json<br/>persona · relationship · index"]
Prompt["src/prompts/abby.system-prompt.md<br/>behavior contract"]
Knowledge["content/abby/*.md<br/>public knowledge files"]
Loader["lib/abby-knowledge.ts<br/>knowledge loader"]
API["/api/abby<br/>conversation endpoint"]
Abby["Abby Response<br/>safe public guidance"]
Profile["personal-profile.md"]
Journey["professional-journey.md"]
Speaking["speaking-profile.md"]
Thought["thought-leadership.md"]
Works["projects-and-works.md"]
Media["media-kit.md"]
Contact["contact-and-collaboration.md"]
Boundaries["public-boundaries.md"]
FAQ["faq.md"]
Profile --> Knowledge
Journey --> Knowledge
Speaking --> Knowledge
Thought --> Knowledge
Works --> Knowledge
Media --> Knowledge
Contact --> Knowledge
Boundaries --> Knowledge
FAQ --> Knowledge
Config --> API
Prompt --> API
Knowledge --> Loader
Loader --> API
API --> Abby
classDef config fill:#EEF2FF,stroke:#4F46E5,color:#312E81,stroke-width:2px;
classDef prompt fill:#FDF2F8,stroke:#DB2777,color:#831843,stroke-width:2px;
classDef knowledge fill:#ECFDF5,stroke:#059669,color:#064E3B,stroke-width:2px;
classDef file fill:#FEF3C7,stroke:#D97706,color:#78350F,stroke-width:2px;
classDef api fill:#E0F2FE,stroke:#0284C7,color:#075985,stroke-width:2px;
classDef output fill:#F0FDFA,stroke:#0D9488,color:#134E4A,stroke-width:2px;
class Config config;
class Prompt prompt;
class Knowledge,Loader knowledge;
class Profile,Journey,Speaking,Thought,Works,Media,Contact,Boundaries,FAQ file;
class API api;
class Abby output;
| File | Purpose |
|---|---|
content/abby/personal-profile.md |
Founder identity, biography, and reusable public answers. |
content/abby/professional-journey.md |
Career timeline and transition narrative. |
content/abby/speaking-profile.md |
Speaking topics, stage bio, and event-introduction material. |
content/abby/thought-leadership.md |
Principles, worldview, and conceptual positioning. |
content/abby/projects-and-works.md |
Project catalogue and filtering guidance. |
content/abby/founder-narrative-pages.md |
Kisah Sentra, Human – AI Collab, and Tanpa Naskah page summaries. |
content/abby/media-kit.md |
Press materials and interview support. |
content/abby/contact-and-collaboration.md |
Outreach routing and collaboration boundaries. |
content/abby/public-boundaries.md |
What Abby can say, cannot say, and must not infer. |
content/abby/faq.md |
Frequently asked questions and canonical answers. |
Supporting configuration:
| File | Purpose |
|---|---|
src/config/abby.config.json |
Core behavior and API settings. |
src/config/abby.persona.json |
Personality and tone configuration. |
src/config/abby.relationship.json |
Relationship and context rules. |
src/config/abby.knowledge-index.json |
Knowledge file indexing. |
src/prompts/abby.system-prompt.md |
System-level instruction contract. |
flowchart LR
Request["Visitor Request"]
Selector["AI_PROVIDER<br/>environment selector"]
Gemini["Gemini<br/>default Abby provider"]
DeepSeek["DeepSeek<br/>alternate Abby provider"]
OpenAI["OpenAI<br/>alternate Abby provider"]
Nvidia["NVIDIA NIM<br/>legacy /api/chat only"]
Response["Safe Public Reply"]
Request --> Selector
Selector -->|AI_PROVIDER=gemini| Gemini
Selector -->|AI_PROVIDER=deepseek| DeepSeek
Selector -->|AI_PROVIDER=openai| OpenAI
Request -->|legacy path| Nvidia
Gemini --> Response
DeepSeek --> Response
OpenAI --> Response
Nvidia --> Response
classDef request fill:#FEFCE8,stroke:#CA8A04,color:#713F12,stroke-width:2px;
classDef selector fill:#F1F5F9,stroke:#475569,color:#334155,stroke-width:2px;
classDef gemini fill:#EEF2FF,stroke:#4F46E5,color:#312E81,stroke-width:2px;
classDef deepseek fill:#ECFDF5,stroke:#059669,color:#064E3B,stroke-width:2px;
classDef openai fill:#E0F2FE,stroke:#0284C7,color:#075985,stroke-width:2px;
classDef nvidia fill:#DCFCE7,stroke:#65A30D,color:#365314,stroke-dasharray: 5 5,stroke-width:2px;
classDef response fill:#FDF2F8,stroke:#DB2777,color:#831843,stroke-width:2px;
class Request request;
class Selector selector;
class Gemini gemini;
class DeepSeek deepseek;
class OpenAI openai;
class Nvidia nvidia;
class Response response;
| Provider mode | Endpoint | Status | Notes |
|---|---|---|---|
AI_PROVIDER=gemini |
/api/abby |
Primary | Default Abby provider (via Gemini's OpenAI-compatible endpoint). |
AI_PROVIDER=deepseek |
/api/abby |
Alternate | Provider abstraction path. |
AI_PROVIDER=openai |
/api/abby |
Alternate | Provider abstraction path. |
NVIDIA_API_KEY |
/api/chat |
Legacy | Secondary chat route; not the primary Abby system. |
Main Abby conversation endpoint.
Request:
{
"message": "Who is dr Ferdi Iskandar?",
"visitorMode": "public_visitor",
"history": []
}Response:
{
"reply": "dr Ferdi Iskandar is a physician, hospital CEO, and founder building work at the intersection of healthcare, leadership, and artificial intelligence."
}Operational behavior:
| Feature | Implementation |
|---|---|
| Rate limiting | Per-IP fixed window, 20 requests per 60 seconds. |
| Provider switching | Controlled by AI_PROVIDER. |
| Request validation | Message required, 1–2000 characters. |
| Timeout protection | 28 seconds for Abby, 25 seconds for legacy chat. |
| Error mapping | Safe, non-leaking upstream error responses. |
| Output normalization | Plain text, no Markdown. |
| Cache control | Cache-Control: no-store on API responses. |
Legacy chat endpoint powered by NVIDIA NIM.
Status: secondary path. Abby remains the primary AI experience.
flowchart TD
Input["Visitor Question"]
Public["Public Profile Question"]
Clinical["Clinical / Medical Request"]
Private["Private / Unverified Claim"]
Site["Website Navigation Request"]
Allowed["Allowed<br/>Answer from public knowledge"]
Redirect["Safe Redirect<br/>Non-diagnostic + route to appropriate context"]
Refuse["Do Not Answer as Fact<br/>Avoid private or unsupported claim"]
Input --> Public
Input --> Clinical
Input --> Private
Input --> Site
Public --> Allowed
Site --> Allowed
Clinical --> Redirect
Private --> Refuse
classDef input fill:#F8FAFC,stroke:#475569,color:#334155,stroke-width:2px;
classDef allowed fill:#ECFDF5,stroke:#059669,color:#064E3B,stroke-width:2px;
classDef caution fill:#FEF3C7,stroke:#D97706,color:#78350F,stroke-width:2px;
classDef blocked fill:#FEE2E2,stroke:#DC2626,color:#7F1D1D,stroke-width:2px;
classDef public fill:#DBEAFE,stroke:#2563EB,color:#1E3A8A,stroke-width:2px;
class Input input;
class Public,Site public;
class Clinical caution;
class Private blocked;
class Allowed allowed;
class Redirect caution;
class Refuse blocked;
Abby is not:
- a medical diagnosis engine;
- a medical device;
- a triage system;
- an EMR workflow engine;
- a private decision-maker;
- an authority for unsupported biographical, clinical, or institutional claims.
Abby is allowed to support:
- website navigation;
- public profile explanation;
- project and work summaries;
- speaking and collaboration routing;
- general educational context with non-diagnostic boundaries;
- clarification based on the curated public knowledge base.
flowchart LR
Browser["Browser<br/>public visitor"]
Client["Client UI<br/>Abby widget"]
API["Server API<br/>/api/abby"]
Guard["Validation Layer<br/>length · payload · rate"]
Secrets["Server Secrets<br/>provider keys"]
AI["AI Provider<br/>external runtime"]
Safe["Safe Response<br/>no secret leak"]
Browser --> Client
Client --> API
API --> Guard
Guard --> AI
API -.-> Secrets
Secrets -. server-only .-> API
AI --> Safe
Safe --> Client
classDef browser fill:#FEFCE8,stroke:#CA8A04,color:#713F12,stroke-width:2px;
classDef client fill:#E0F2FE,stroke:#0284C7,color:#075985,stroke-width:2px;
classDef api fill:#EEF2FF,stroke:#4F46E5,color:#312E81,stroke-width:2px;
classDef guard fill:#ECFDF5,stroke:#059669,color:#064E3B,stroke-width:2px;
classDef secret fill:#FEE2E2,stroke:#DC2626,color:#7F1D1D,stroke-width:2px;
classDef safe fill:#F0FDFA,stroke:#0D9488,color:#134E4A,stroke-width:2px;
class Browser browser;
class Client client;
class API api;
class Guard guard;
class Secrets secret;
class AI api;
class Safe safe;
| Area | Current practice |
|---|---|
| Secrets | Server-side only; never exposed to browser or Git. |
| API protection | Rate limiting, request validation, timeout protection, safe errors. |
| Headers | Global security headers configured in next.config.mjs. |
| Dependencies | Audited through pnpm security:deps. |
| Cache | Cache-Control: no-store on AI API responses. |
| Threat model | See docs/security/threat-model.md. |
flowchart TB
subgraph App["Next.js App Router"]
Root["app/layout.tsx<br/>root shell + fonts"]
Pages["Public Routes<br/>home · about · works · notes · speaking · cv"]
Metadata["robots.ts + sitemap.ts<br/>generated metadata"]
end
subgraph Client["Client Experience"]
AbbyWidget["components/AbbyWidget.tsx"]
Visuals["components/visual/*"]
UI["components/ui/*"]
end
subgraph Server["Server Runtime"]
AbbyAPI["app/api/abby/route.ts"]
LegacyAPI["app/api/chat/route.ts"]
RuntimeGuard["scripts/next-runtime-guard.mjs"]
end
subgraph Content["Content and Configuration"]
AbbyContent["content/abby/*.md"]
SiteContent["lib/site-content.ts"]
SiteMetadata["lib/site-metadata.ts"]
AbbyConfig["src/config/*.json"]
AbbyPrompt["src/prompts/*.md"]
end
subgraph Quality["Quality System"]
Tests["tests/*"]
Vitest["Vitest"]
ESLint["ESLint"]
Typecheck["TypeScript"]
Build["Production build"]
end
Root --> Pages
Pages --> AbbyWidget
Pages --> Metadata
AbbyWidget --> AbbyAPI
AbbyAPI --> AbbyContent
AbbyAPI --> AbbyConfig
AbbyAPI --> AbbyPrompt
LegacyAPI --> Server
SiteContent --> Pages
SiteMetadata --> Metadata
Tests --> Vitest
Typecheck --> Build
ESLint --> Build
RuntimeGuard --> Build
classDef app fill:#DBEAFE,stroke:#2563EB,color:#1E3A8A,stroke-width:2px;
classDef client fill:#FDF2F8,stroke:#DB2777,color:#831843,stroke-width:2px;
classDef server fill:#EEF2FF,stroke:#7C3AED,color:#312E81,stroke-width:2px;
classDef content fill:#ECFDF5,stroke:#059669,color:#064E3B,stroke-width:2px;
classDef quality fill:#FEF3C7,stroke:#D97706,color:#78350F,stroke-width:2px;
class Root,Pages,Metadata app;
class AbbyWidget,Visuals,UI client;
class AbbyAPI,LegacyAPI,RuntimeGuard server;
class AbbyContent,SiteContent,SiteMetadata,AbbyConfig,AbbyPrompt content;
class Tests,Vitest,ESLint,Typecheck,Build quality;
| Component | Depends on | Provides |
|---|---|---|
app/layout.tsx |
Fonts, smooth scroll provider, global layout | Root application shell |
app/page.tsx |
Site content, visual components | Editorial homepage |
components/AbbyWidget.tsx |
/api/abby |
Public AI assistant overlay |
app/api/abby/route.ts |
Provider SDKs, knowledge loader, prompt config | Main Abby conversation endpoint |
app/api/chat/route.ts |
NVIDIA NIM SDK | Legacy chat endpoint |
lib/abby-knowledge.ts |
content/abby/*.md |
Structured knowledge loading |
lib/site-content.ts |
Curated copy data | Route-level content |
lib/site-metadata.ts |
Site content and metadata rules | Route-aware metadata builder |
scripts/next-runtime-guard.mjs |
Runtime lock file | Build/dev process protection |
apps/corporate/ferdiiskandar/
├── app/ # Next.js App Router routes
│ ├── about/ # About page
│ ├── api/
│ │ ├── abby/route.ts # Main Abby assistant endpoint
│ │ └── chat/route.ts # Legacy NVIDIA chat endpoint
│ ├── cv/ # CV route
│ ├── globals.css # Primary editorial stylesheet
│ ├── layout.tsx # Root layout with fonts/providers
│ ├── page.tsx # Homepage entry
│ └── robots.ts / sitemap.ts # Generated metadata
├── components/ # React components
│ ├── ui/ # Shared UI primitives
│ ├── visual/ # Visual and motion components
│ └── *.tsx # Page-level feature components
├── content/abby/ # Abby knowledge base Markdown files
├── docs/ # Architecture, specs, reports, governance, archive docs
├── lib/ # Utilities, content data, hooks
├── public/ # Static assets and images
│ ├── icons/ # Tech provider icons
│ └── images/ # Team and product photos
├── src/
│ ├── config/ # Abby JSON configs
│ └── prompts/ # System prompts
├── tests/ # Vitest and Playwright tests
└── scripts/ # Build/runtime guards
# 1. Install dependencies from monorepo root
pnpm install
# 2. Move into the app directory
cd apps/corporate/ferdiiskandar
# 3. Copy environment template
cp .env.example .env.local
# 4. Add AI provider credentials
# AI_PROVIDER=gemini
# GEMINI_API_KEY=your-key-here
# 5. Start the development server
pnpm dev
# 6. Open the local site
# http://localhost:3000From monorepo root:
pnpm install
pnpm --filter @the-abyss/ferdiiskandar devFrom app directory:
cd apps/corporate/ferdiiskandar
pnpm install
pnpm devProduction build:
pnpm build
pnpm start# AI Provider selection: "gemini" default, or "deepseek" / "openrouter" / "openai"
AI_PROVIDER=gemini
# Gemini required when AI_PROVIDER=gemini (uses Gemini's OpenAI-compatible endpoint)
GEMINI_API_KEY=
# ABBY_MODEL=gemini-3.1-flash-lite
# DeepSeek required when AI_PROVIDER=deepseek
# DEEPSEEK_API_KEY=
# DEEPSEEK_BASE_URL=https://api.deepseek.com
# ABBY_MODEL=deepseek-chat
# OpenAI required when AI_PROVIDER=openai
# OPENAI_API_KEY=
# ABBY_MODEL=gpt-4o-mini
# Legacy only, used by /api/chat. Not required for Abby.
NVIDIA_API_KEY=Rules:
- Use
.env.localfor local secrets. - Do not commit provider keys.
- Do not expose provider keys to browser code.
- Keep
/api/chatas legacy unless intentionally reactivated. - Keep Abby's primary contract on
/api/abby.
The build process is protected by scripts/next-runtime-guard.mjs.
flowchart LR
Dev["pnpm dev"]
Lock[".next-runtime-lock.json"]
Build["pnpm build"]
Guard["Runtime Guard"]
Pass["Build Allowed"]
Block["Build Blocked<br/>active dev server detected"]
Dev --> Lock
Build --> Guard
Guard -->|no active lock| Pass
Guard -->|active lock| Block
Lock --> Guard
classDef dev fill:#DBEAFE,stroke:#2563EB,color:#1E3A8A,stroke-width:2px;
classDef lock fill:#FEF3C7,stroke:#D97706,color:#78350F,stroke-width:2px;
classDef pass fill:#DCFCE7,stroke:#16A34A,color:#14532D,stroke-width:2px;
classDef block fill:#FEE2E2,stroke:#DC2626,color:#7F1D1D,stroke-width:2px;
class Dev,Build,Guard dev;
class Lock lock;
class Pass pass;
class Block block;
The guard prevents accidental build execution while a dev runtime is active in the same app workspace.
| Command | Purpose |
|---|---|
pnpm typecheck |
TypeScript type checking. |
pnpm lint |
ESLint with --max-warnings=0. |
pnpm test |
Run Vitest suite once. |
pnpm test:watch |
Run Vitest in watch mode. |
pnpm test:coverage |
Run Vitest with coverage report. |
pnpm build |
Production build. |
pnpm security:deps |
Dependency security audit, app-scoped. |
pnpm knip |
Dead-code and unused export detection. |
Current test contracts:
- sitemap contract;
- site metadata contract;
- site content contract;
- Next runtime guard behavior;
- smoke tooling baseline;
- navbar route awareness;
- about page rendering.
Coverage thresholds: 80% for lines, functions, branches, and statements.
flowchart TD
Change["Code or content change"]
Typecheck["pnpm typecheck"]
Lint["pnpm lint"]
Test["pnpm test"]
Coverage["pnpm test:coverage"]
Build["pnpm build"]
Security["pnpm security:deps"]
Review["Manual Abby behavior review"]
Release["Safe to release"]
Change --> Typecheck
Typecheck --> Lint
Lint --> Test
Test --> Coverage
Coverage --> Build
Build --> Security
Security --> Review
Review --> Release
classDef change fill:#E0F2FE,stroke:#0284C7,color:#075985,stroke-width:2px;
classDef quality fill:#ECFDF5,stroke:#059669,color:#064E3B,stroke-width:2px;
classDef security fill:#FEF3C7,stroke:#D97706,color:#78350F,stroke-width:2px;
classDef release fill:#FDF2F8,stroke:#DB2777,color:#831843,stroke-width:2px;
class Change change;
class Typecheck,Lint,Test,Coverage,Build quality;
class Security,Review security;
class Release release;
No public claim without controlled context.
No AI answer without boundary awareness.
No clinical guidance without non-diagnostic limits.
No API route without validation and timeout protection.
No deployment without build, typecheck, test, and security review.
| Question | Required answer |
|---|---|
| What public problem does this solve? | It helps visitors understand the founder, work, routes, and collaboration surfaces. |
| Who is accountable? | The founder/site owner remains accountable for public content and positioning. |
| What is outside scope? | Diagnosis, treatment advice, private medical interpretation, and unsupported claims. |
| What can fail? | Provider outage, missing API keys, stale knowledge, route regression, unsafe prompt drift. |
| How is it verified? | Build, typecheck, lint, tests, coverage, dependency audit, and manual Abby behavior checks. |
timeline
title Founder Dossier Roadmap
v0.1.x : Founder dossier stabilization
: /about route release
: baseline Abby knowledge
v0.2.x : Homepage repositioning
: cross-sector public profile copy
: Abby knowledge refinement
Next : /systems route
: /contact route
: Abby visitor guidance refinement
Later : richer media kit
: public writing cadence
: formal collaboration intake
| Target | Focus | Status |
|---|---|---|
v0.1.x |
Founder dossier stabilization | Released |
v0.1.x |
/about route, layered authority page |
Released |
v0.1.x |
Abby knowledge refinement | Active |
v0.2.x |
Homepage content repositioning, cross-sector | Active |
v0.2.x |
/about copy repositioning |
Active |
| Later | /systems route |
Planned |
| Later | /notes route |
Planned |
| Later | /contact route |
Planned |
| Later | Abby UX and visitor guidance refinement | Planned |
See docs/governance/contributing.md for development workflow, coding standards, and pull request requirements.
Recommended rule:
Keep public content clear.
Keep Abby bounded.
Keep routes intentional.
Keep API behavior safe.
Keep verification repeatable.
MIT License — see LICENSE for details.
Architected and maintained as part of the Sentra Artificial Intelligence ecosystem.
Founder dossier infrastructure · Abby AI Assistant · public profile intelligence · controlled editorial surface.