Zero to hero course
Learn Iris from the business process to a saved command. Finish with a source trace, a safe change exercise, and a director review rehearsal.
Choose your reading path
| Need | Read in this order | You should be able to |
|---|---|---|
| Meeting within a day | Decision brief, costs, FAQ, then lessons 1, 3 and 6 | Give the funding ask, explain the demo limits, and name the next decision owners. |
| Understand the code | All six lessons, then the existing system pages and file notes | Trace a user action through UI, server, rules, storage, reports, and tests. |
| Plan the real app | Production architecture, roadmap, testing, program expansion | Describe boundaries, release gates, staff commitments, and how to add a program. |
Six lessons
| Lesson | Time allowance | Output |
|---|---|---|
| 1. Business process and basic terms | 90 minutes | A review lifecycle and a plain explanation of each role. |
| 2. Browser, server, and code map | 2 hours | A traced request and a stack decision table. |
| 3. Review commands, calculations, and workflow | 3 hours | A save trace, calculation example, and explanation of blocked approvals. |
| 4. Identity, persistence, access, and evidence | 2 hours | A conflict walkthrough and data access checklist. |
| 5. Intake, search, reporting, and operations | 2 hours | An import-to-export map with integration limits. |
| 6. Change lab and meeting rehearsal | 2 to 4 hours | A small reviewed change plan and a five-minute funding pitch. |
Evidence rules
- Current: behavior found in the inspected source. Link to the governing specification and relevant source before claiming it works.
- Historical: a dated result in implementation status. It does not prove the current checkout passes.
- Proposed: architecture, budget, staff, targets, and future behavior in this pack.
- Open: a decision that needs management, policy, IT, procurement, or receiving-system approval. Keep its owner and release impact visible.
The current demo only implements SNAP Negative. The user built it to demonstrate a useful interface and clarify requirements. Treat it as a reference for a new production build. Reuse a component only after an engineer reviews its behavior, tests, license, and fit.
Completion standard
- Explain the workflow and six roles without using file names.
- Trace one save from a field edit to the next snapshot and inbox event.
- Explain all six version/identity values in lesson 4.
- Find the tests for one rule and explain what they do not prove.
- Identify the non-drop routing blocker, external EPP boundary, and federal export boundary.
- Describe the proposed production architecture and one complete program addition.
- Give the cost range with assumptions and the stage-one funding ask.
- Answer the rehearsal questions accurately. Use an open decision when evidence is absent.
This course provides a full map of the demo, not a claim that reading replaces engineering review. For file-by-file orientation, use the existing file notes. For intended behavior use the active specification. For unresolved policy use the knowledge register.