Program Map
Vedya is a capability ladder. It starts with basic computing fluency and ends with forward deployed engineering: working with users, systems, agents, and production constraints.
How The Modules Build On Each Other
Section titled “How The Modules Build On Each Other”capability ladder
00 OrientationSee software as a running system.
01 SystemsSplit products into components and boundaries.
02 ProgrammingMake behavior repeatable with code.
03 DataDesign what the system remembers.
04 APIsConnect systems through contracts.
05 ProductShip a feature from UI to database.
06 QualityTest, debug, and prove fixes.
07 OpsDeploy, observe, and rollback.
08 SDLCRun the professional change lifecycle.
09 ADLCDelegate to agents with verification.
10 FDEDeliver in real user constraints.
CapstoneProve the whole loop end to end.
Module Outcomes
Section titled “Module Outcomes”| Module | What They Learn | What They Produce | What It Proves |
|---|---|---|---|
| 00 Orientation | How software work actually happens | System map and engineering log | They can observe before acting |
| 01 Systems | Components, boundaries, failures | Architecture and failure diagram | They can reason beyond code files |
| 02 Programming | Control flow, data structures, functions, modules | CLI app with tests | They can make machines repeat behavior |
| 03 Data | Schemas, state, queries, migrations | Data model and migration plan | They understand what the system remembers |
| 04 Web/API | HTTP, contracts, auth, integration | API contract and mock endpoint | They can connect systems safely |
| 05 Product | UI-to-database feature slices | Complete feature path | They can convert user intent into behavior |
| 06 Quality | Tests, debugging, logs, root cause | Reproduced bug and postmortem | They can fix the cause, not the symptom |
| 07 Ops | Deploy, config, secrets, health, rollback | Runbook and operational proof | They can keep software alive |
| 08 SDLC | Requirements through release | Design, task plan, release plan | They can run a professional change lifecycle |
| 09 ADLC | Agentic decomposition and verification | Agent task logs and reviewed output | They can use agents without surrendering judgment |
| 10 FDE | User workflows, constraints, adoption | Field delivery handoff | They can deliver in real conditions |
Weekly Fast Track
Section titled “Weekly Fast Track”This is aggressive, but useful for someone who needs to become deployable fast.
| Week | Focus | Required Labs |
|---|---|---|
| 1 | Environment, terminal, Git, code, systems, data | Setup, Labs 1, 2, 3 |
| 2 | Feature building, API, tests, debugging | Starter project, Labs 4, 5, failure fixtures |
| 3 | Deployment, operations, SDLC | Lab 6, phase gates 1-5 |
| 4 | ADLC, field delivery, capstone | Lab 7, phase gates 6-7, capstone |
Deep Track
Section titled “Deep Track”Spend one week per module. For each week:
- Read one module.
- Complete at least one lab.
- Add one portfolio artifact.
- Ask an agent to review the artifact.
- Fix the artifact after review.
- Write what you misunderstood.
Portfolio Evidence
Section titled “Portfolio Evidence”00 Orientationsystem-map.md
engineering-log.md
engineering-log.md
01 Systemsarchitecture-diagram.md
failure-modes.md
failure-modes.md
02 Programmingtask-tracker/
test-results.md
test-results.md
03 Dataschema.md
queries.sql
migration-plan.md
queries.sql
migration-plan.md
04 APIsapi-contract.md
curl-evidence.md
curl-evidence.md
05 Productfeature-slice.md
acceptance-tests.md
acceptance-tests.md
06 Qualityreproduction.md
fix.md
postmortem.md
fix.md
postmortem.md
07 Opsrunbook.md
rollback-proof.md
rollback-proof.md
08 SDLCdesign-doc.md
release-plan.md
release-plan.md
09 ADLCagent-tasks.md
verification-log.md
verification-log.md
10 FDEworkflow-map.md
user-handoff.md
user-handoff.md
Capstonedemo-script.md
source-or-link.md
runbook.md
retrospective.md
source-or-link.md
runbook.md
retrospective.md
Required Practice System
Section titled “Required Practice System”All learners should use Support Desk Mini unless an instructor assigns a different app. It exists so every learner can practice the same lifecycle:
starter project loop
RunStart the app locally.
InspectFind files, routes, state, tests.
TraceFollow one request end to end.
ChangeMake one scoped behavior update.
TestProve expected behavior.
BreakTrigger a controlled failure.
DebugFind the cause with evidence.
OperateWrite runbook and rollback notes.
The starter project has:
- HTTP API.
- SQLite persistence.
- Business rules.
- Audit events.
- Human approval.
- Tests.
- Bug modes for debugging drills.
Phase Gates
Section titled “Phase Gates”Use phase gates after major sections. A learner should not move to capstone until they pass the first seven gates.
The Learning Loop
Section titled “The Learning Loop”Every module uses the same loop:
learning loop
SeeObserve existing behavior.
NameIdentify the concept.
DrawMap flow, state, or dependency.
BuildCreate a small working version.
BreakIntroduce a controlled failure.
DebugFind the cause with evidence.
VerifyProve the fix works.
ExplainTeach it back plainly.
- See: observe an existing system or behavior.
- Name: identify the concepts involved.
- Draw: represent flow, state, or dependency.
- Build: create a small working version.
- Break: introduce a controlled failure.
- Debug: find the cause with evidence.
- Verify: prove the fix works.
- Explain: teach it back in plain language.
Minimum Bar Per Module
Section titled “Minimum Bar Per Module”A module is not complete until the learner can:
- Explain the idea without jargon.
- Point to where it appears in a real system.
- Produce a diagram.
- Run or build something.
- Show one failure mode.
- Show verification evidence.
- Answer “what would break if this assumption is wrong?”