Illustrative release reviewWhat did we know then?
Tap a dated record to see what the team knew.
Monday meeting note
Friday is the agreed launch date.
Tuesday test report
Sign-in failed. The agreed launch date remains Friday.
Wednesday morning proposal
Moving launch to Monday is proposed. Friday still governs.
Wednesday afternoon decision
The owner approves Monday. Readiness remains unknown because no passing retest is recorded.
J6 / Owner-described configurationRun local AI
J6.1 · What would I hold?
In the owner-described setup, you hold Qwen3 1.7B weights and a task adapter, with Ollama running inference on your machine.
J6.2 · What does the adapter learn?
A repeatable review task, such as citing release evidence, identifying blockers and asking for the next verification.
J6.3 · Where does training happen?
A dedicated or rented GPU trains the adapter. Your own machine runs everyday inference.
J6.4 · Where do changing facts live?
Keep today's test result and launch date in the knowledge base. Updating those records does not require retraining the adapter.
J6.5 · Can I complete the task locally?
The proposed local path supplies retrieved passages to Ollama. Installation requires acquiring the model and adapter first.
J6.6 · How do I test specialization?
Give the base and adapted models identical unseen cases. Score citations, missed blockers, unsupported claims and justified abstentions.
J6.7 · What if the model gets it wrong?
Inspect the source, correct or reject the draft, and retain authority over the maintained record.
J6.8 · How do I verify availability?
Check release-specific packaging, model compatibility and license terms before adopting this owner-described configuration.
J6.9 · What is still unmeasured?
The supplied material gives no blind evaluation scores, hardware minimums or measured inference latency.
↑ Back to mapJ8 / Illustrative caseReview a release
J8.1 · What date was agreed on Tuesday?
Friday. Tuesday's failed test introduced a blocker but did not change the schedule.
J8.2 · Why did the owner move launch?
Wednesday's proposal cited Tuesday's sign-in failure. The owner approved moving the target to the following Monday.
J8.3 · How could local AI help?
Draft a cited assessment identifying the failed test and requesting a passing retest.
J8.4 · Who changed the plan?
The release owner approved it Wednesday afternoon. The morning proposal had no authority to change the baseline.
J8.5 · Are we ready to ship?
Readiness is undetermined. The supplied records establish a new target date and contain no passing sign-in retest.
J8.6 · How do I check for missing evidence?
Inspect the meeting note, test report, proposal and decision record. No retest appears in this four-record packet.
J8.7 · What should the interface clarify?
How it will distinguish schedule approval from a missing readiness check remains an open design question.
↑ Back to map