Version v0.15.31
Released Jul 1, 18:40
Lines 89,155
All tests [0/356]

This site was built using automated SDLC workflow.

// AI-Augmented Development

From Idea to Deployment: A Practical
AI-Augmented Development Workflow

A platform of tools, experiments, and real-world implementations — focused on building reliable, scalable human – AI collaboration systems

20+ Years
50+ Projects
14 Sectors
Scroll to explore
Version v0.15.31
Released Jul 1, 18:40
Lines 89,155
All tests [0/356]

Framework

How the work gets built.

The AI-fluency methodology behind every build — evolution, the four disciplines, prompt engineering, the SDLC, and the knowledge base.

Effective AI collaboration starts with a clear division of responsibility. Not everything should be delegated, and not everything should be manual. Every task begins with sbx sdlc init — I define the scope, choose which applications and packages are affected, set the action type. The system derives everything else: which steps apply, which domain experts to load, which standards are relevant.

Andrei
Andrei
Architect
Owns the WHY
  • Defines goals and user stories
  • Makes architectural decisions
  • Reviews, approves, deploys
  • Strategy, UX, business logic
222+ decision records authored
Claude
Claude
Implementer
Owns the HOW
  • Implements code from specifications
  • Follows governed constraints
  • Runs builds, tests, checks
  • Step-by-step criteria execution
1,035 workspace nodes maintained

The quality of AI output is bounded by the quality of context it receives. Manual prompt engineering doesn't scale — you can craft a perfect prompt once, but not hundreds of times across a real project. SBX replaces manual prompting with automated context engineering. Each SDLC step generates a structured prompt with contextual knowledge injection.

1 Knowledge Artifacts 352
2 Step Context FDD phase
3 Application Awareness platform + layer
4 Success Criteria measurable gates
5 Reference Examples proven code
6 Constraints scope bounds
Manual prompt
"Write me a login component"
Context-engineered
User story S-042 + design tokens + SSR load pattern + 3 reference components + 12 constraints + verification criteria

AI can produce plausible-looking output that's subtly wrong. Discernment means building evaluation into the process itself, not relying on human vigilance alone. The Description-Discernment loop is embedded in the SDLC state machine — not optional, not skippable. Six gates stand between AI output and production.

01
Governance hooks
Pre-commit hooks validate code style and enforce banned patterns. bash-deny-revalidate.sh blocks raw platform commands — go, npm, node are intercepted. Everything flows through sbx CLI wrappers.
$ npm install → BLOCKED. Use: sbx build --platform svelte --dir <path>
02
Scope guards
Each SDLC task defines which files, packages, and applications are in scope. The inductive trace at topic close checks every changed file against the originating story. Changes outside scope get flagged as a separate task.
Task scoped to core-ui touches infrastructure/docker/ → RED FLAG: out of scope
03
Story traceability
Every exported function must trace to a user story. sbx sdlc complete blocks at FDD5.CONFORMANCE if traceability is missing. Code without a traceable requirement has no reason to exist — and can be deleted.
loadPortfolioSections() → Story S-042 "Portfolio filtering by platform"
04
Build verification
sbx build and sbx check must pass with zero errors. Type checking (svelte-check, go vet) runs automatically. Build output must show exit code 0. No "it compiles on my machine."
$ sbx check --platform svelte → 0 errors, 35 warnings (baseline)
05
Runtime proof
"Done" is not accepted without evidence. Build output (exit 0) + HTTP 200 on target URL + screenshot for UI work. If verification is blocked, must say "PENDING — blocked by [reason]" — never "done."
$ curl -s -o /dev/null -w "%{http_code}" http://localhost:4000/framework → 200
06
Conformance check
5-step inductive trace before any topic closes: git status, file-story mapping, cross-check against topic scope, knowledge reconciliation, active task reconciliation. Two minutes, non-negotiable.
git diff --stat HEAD → 4 files changed → all mapped to Story S-047 → PASS

When AI helps produce your work, you're still responsible for it. Every decision is immutable and auditable. Every exported function traces to a user story. PR workflow is mandatory — direct push to main is blocked by hooks. This website is the diligence statement: built entirely with AI-augmented development, every commit traceable.

222+
Immutable decision records
proposed → decided → superseded → archived
100%
Story traceability
function → story → goal
BLOCKED
Direct push to main
PR workflow enforced by hooks
OWASP
Security domain expert
credential masking + GDPR awareness

Process

From idea to production, governed end to end.

The end-to-end development process, grounded in a catalogue of industry standards and practices — from goal definition through model, plan, build, and verification.

Games

Playable browser games built through the AI-augmented process.

DATAWORM

// NEURAL DATA EXTRACTION PROTOCOL v9.0

> GRID: 20x20 SECTORS

> OBJECTIVE: CONSUME DATA PACKETS

> LIVES: 3 (EXTRA LIFE PICKUPS ENABLED)

> PORTALS: ACTIVE (BORDER WARP NODES)

> WARNING: SELF-COLLISION IS FATAL

PRESS [ENTER] TO INITIATE