Establish · Optional exploration
Move a prototype into shared use
A working CSV exporter is ready for a demo. What would make it ready for a team's weekly report?
Think it through with your agent
Give your agent this URL. It contains the scenario and guidance to ask one question at a time. Start with your own prediction or explanation, then check it against the book.
Use with your task. Establish the evidence baseline. Keep discoveries in your existing evidence or learning notes.
Follow the argument. Assign authority and ownership.
Read the exercise
Scenario#
Invented paper scenario. A colleague uses an agent to build a CSV exporter for the event tracker; it correctly exports one selected workspace's event types and timestamps from synthetic data. The colleague and agent have permission to work only in the sandbox. The colleague now asks to use it for the team's weekly report with live data. For this fixture, each reader may export only their authorized workspace and the two named fields. No operational owner or production access has been agreed.
Investigate#
- State what the demonstration establishes and which claims about shared use remain untested. How would you check that changing a workspace identifier cannot expose another workspace's events?
- Propose the smallest useful trial within an explicitly granted scope. Name who may access which data, who may deploy, what evidence permits each transition, and when the workflow must stop or return for a decision.
- Assign an owner for correction, support, and retirement; define a rollback trigger and recovery path. If the exporter has already written an out-of-scope CSV file, what can reverting its code undo, and what obligation remains?
- Define a period for assessing useful accepted reports, time saved, and recurring review, correction, and support effort. Which result would justify expanding access, revising the workflow, or retiring it?
Keep the proposed trial and remaining unknowns in the existing discussion or learning notes. This exercise requires no live data, deployment, or additional project feature.
Further reading#
Geoffrey Huntley's essay on organizational access argues for enabling more people to create software while engineering the controls around shared use. Treat this as a practitioner proposal to examine: easier code generation leaves data access, deployment authority, and ongoing support to be settled.
Show worked reasoning
The demonstration establishes the checked export behavior on synthetic data. A first trial can stay in the sandbox and test an authorized workspace, rejection of another workspace, and the exact exported fields. Supplying a workspace identifier is not evidence of permission: the application must enforce the reader's access independently of the interface. A later live trial needs explicit data and deployment authority, checks on the actual configuration, and an owner able to stop the trial and restore the previous reporting path. The current sandbox permission does not grant that transition.
Disabling the faulty export path can stop new exports but cannot retract a file already copied elsewhere. The owner must also address the affected data under the applicable incident process. Agree on a bounded observation period and compare accepted reports and time saved with review, corrections, and support effort, including unfinished work. Expansion depends on those outcomes and the agreed access rules; the ability to generate the tool alone does not settle whether it is useful to operate.
This is optional, ungraded exploration. The course brief defines the required work.