Streamlit shell
The public question input and assistant message shell are on dev. It still displays placeholder text.
ECCU STEMNisa build · student workspace
Learn · build · prove
Today · Monday 27 July · Day 11
Review. Scrum. Leave with the next build.
The authority routes are agreed. Today’s job is to protect the current work, align the shared answer contract and move one synthetic question from service to screen.
Protect the current work before changing branches
The local student notebook has uncommitted work on dev. Identify its owner and preserve it on an appropriate branch or reviewed commit before any switch, pull or integration work.
Part 1 · Review
What the repository actually proves
Snapshot inspected from the current local clone on 27 July. “Present” is not the same as “integrated,” and a commented test is not a passing test.
First user journey
The journey document and three agreed authority examples are merged.
Authority route
general, personal and secure routes exist. The broad “I / my” rule has a known over-blocking challenge.
Learning notebooks
Class notebooks through Day 15 are present; the student practice notebook has uncommitted local work.
Live Issue ledger · #7–#14
Discussion is evidence of thinking—not evidence of completion
Evidence present
Journey document is merged; selected questions are visible in the Issue comment.
Completion gap
Issue remains open with unchecked success checks; user, exact reviewed source, proof and confirmation owners are incomplete.
Evidence present
Streamlit shell is merged and an early answer attempt is preserved in the Issue comment.
Completion gap
No supported end-to-end answer exists. The attempted Boolean expression is incorrect and the factual wording is unreviewed.
Evidence present
The Issue contains a useful range of personal, amount, contribution, status and identity examples.
Completion gap
Only the three simple routes are executable; there is no proof that stopped questions never reach search.
Evidence present
The Issue identifies source labels, date context, limitations and withholding when metadata is incomplete.
Completion gap
The shared answer/evidence structure and evidence completeness check are still TODOs.
Evidence present
Comments distinguish empty, malformed, unsupported, missing-source and service-error behaviour.
Completion gap
service.py remains unimplemented and the fallback behaviours are not executable or tested.
Evidence present
Several respectful boundary and next-step messages have been drafted.
Completion gap
The official route remains review-pending; handoff.py and its no-personal-data test are unfinished.
Evidence present
The Issue identifies distinct states, mobile layout, contrast and the limits of automated accessibility checks.
Completion gap
The screen still shows one placeholder response and is not connected to the shared result contract.
Evidence present
Three authority-route tests are executable and the required scenario categories are documented.
Completion gap
The remaining suites are comments or TODOs; pytest is not installed in the current local environment.
Still open
- Agree and implement one shared answer/evidence dictionary contract in models.py.
- Connect Streamlit to answer_question() through service.py.
- Add one synthetic reviewed record and deterministic search path.
- Implement reason-specific handoff wording without requesting personal data.
- Turn commented test starters into executable tests across the full path.
- Add pytest to the managed development environment before claiming a green suite.
Part 2 · Actual Scrum
Thirty minutes, then build
0–5 min
Review
Confirm the repository facts below. Do not reopen agreed routing.
5–17 min
Pair round
Each workstream gives evidence, today’s outcome and one precise blocker.
17–24 min
Dependency huddle
Contract owners show the proposed keys; all consuming streams accept or challenge them.
24–30 min
Commit
Name the branch, first file, check and reviewer. Then leave the meeting and build.
#7
Journey reviewers
Confirm the first supported question, exact source route and acceptance examples; review the shared contract.
First move
Check that the proposed result states can represent every allowed and blocked example.
Dependency
No coding dependency; provides product acceptance to #10.
0 workstreams have a complete update · 0 marked blocked
Copy the sanitised summary into the team record after the final commitment.
Today’s build after Scrum
One vertical walking skeleton
1. Contract
A synthetic result uses agreed keys for state, text, evidence, reason and record ID.
2. Service
answer_question() returns that result without search, facts or a model.
3. Screen
Streamlit displays the returned text through the service boundary.
Use synthetic text today. Runtime NIS content stays empty until the source, date, limitation and confirmation gate can withhold incomplete evidence.
Part 3 · Tomorrow · Tuesday 28 July · Day 12
Accessible interaction, on the same safe contract
Calendar lesson
Day 12 explores accessibility and voice as progressive enhancement—not as a second product path.
Product gate
Begin the accessible interface only if the shared result contract and one service-to-screen path are integrated.
Required proof
Keyboard journey, narrow-screen check, labelled controls and the same safe fallback when voice is unavailable.
If today slips
Finish the contract and walking skeleton tomorrow morning. Do not hide an integration gap behind a new feature.