vectalon/demo● zero model calls
The feature workflow, live
Type one sentence. Vectalon runs the whole loop — requirement, architecture decision, affected files, implementation plan, code, tests, review, build verification, pull request — and when a gate fails, it diagnoses, modifies, rebuilds, and re-verifies until the build passes. This is the demo, not a promise: it is a real workflow run against the demo app.
$ vectalon feature "Build a Login feature."
The self-healing loop
when a gate failsVerification and readiness are real gates — tsc, jest, lint run against the generated code. When a check fails, the workflow doesn't stop and hand you an error: it extracts the failing facts, sends them back to implementation, regenerates, and retries the gate.
Build failed → diagnose → modify → rebuild → verify
· Build failed — verification or readiness fails
· diagnose — failure facts extracted from the report — which check, what exit code, the first error line
· modify — implementation regenerates with the failure context injected
· rebuild — the failing stage is retried against the new code
· verify — the loop repeats until the gate passes or attempts run out
The workflow
Fourteen phases from PRD to close — every artifact written to docs/vectalon/ in your repo, visible in version control.
The self-healing loop
A failing gate feeds its own failure facts back into implementation. The workflow fixes itself, bounded, until it passes.
The control plane
Intel first, score to measure, fix to repair, mode to control where it runs — this workflow is the whole system in motion.
The 30-minute sales demo
● no explanation requiredThe feature workflow is the hero. The vc sales-demo command is the meeting — five acts, run live against a real React Native repository, every number real, zero model calls, and the fix act touches only a sandbox. These are the real numbers from the demo app:
0–5
1 · init — vectalon init
“Here’s a real React Native repository.”
· 51 files
· 27 components
· 18 screens
· 7 dependencies
Health Score 73/100
5–10
2 · intel — vc intel
“Vectalon understands the application, not just files.”
· 18 screens
· 1 navigation stack
· CartContext state
· 7 dependencies
Dependency graph: no cycles
10–20
3 · fix — vc fix
“Take a real failure.”
· Kotlin 1.7.22 below the 1.9.0 pin
· Root cause + evidence at android/build.gradle
✓ 2 edits applied in sandbox · confidence 72%
20–25
4 · brain — vc brain
“Why did we choose Zustand?”
· adr-017 · Performance + simplicity
· Approved by Architecture Team · March 2026
Related: Cart, Checkout, Profile
25–30
5 · outcomes — vc outcomes
“This is what Vectalon saved your team.”
· 24 issues detected
· 4 issues prevented
· 44.5 engineer-hours
Estimated savings: $3,338
$ vc sales-demo # the whole meeting, one command
$ vc sales-demo --log build.log # bring your own real failure
Every act prints a carbon window with the minute marker, the narration line, and the real output; the full 30-minute script is written to docs/vectalon/sales-demo/SCRIPT.md.
Run it on your own repo — the workflow, the docs, and the healing loop are yours:
$ npx vectalon feature "Build a Login feature."
$ npx vectalon sales-demo