Submit Your Work
What You Turn In
- Your four-checks audit, both pieces (repo link)
- Auth, edge cases, versions, invented libraries on the stock tool and on your own SCS3.5 script, each with a finding and the evidence; 'clean' only with evidence beside it; a coach initialled it
- Your branch scs3.6-patch and the patch card (repo link) fill in on the hub
- A test that fails on the old code and passes on the patch; one prompt word for word; the diff read line by line; the hand adjustment in its own commit; the six-line receipt with rights and cost
- The key out of the code on main (repo link)
- Taken out by hand, read from the environment; you can say why it is still a problem in the history
- Your rules file and one skill, run once (repo link)
- Stack, Tests with the exact command, Never from your audit, Skills; the skill with a name, when, five steps or fewer, how you know, and the date it ran
- Your branch scs3.6-agent and the agent log (repo link)
- One scoped job, the log written as it ran, at least one change rejected with the reason, merged with --no-ff or closed
- Photo of your connector scope card, client's name covered fill in on the hub
- Systems by type, read or write and why, sandbox or copy, what is logged, when revoked, the one thing never connected; nothing connected
- Your cost card, the check-scs3.6 receipt and your method note fill in on the hub
- The day's AI use in shillings at the dated price; the full check PASS; six lines, the sixth the check you ran least carefully
Stuck, or want to check your thinking? Paste this card into your own AI and ask it to question you, not answer for you.
How
- Asha, by the week's update.
Done when
- Four-checks audit, both pieces: All four checks on the stock tool and on the trainee's own SCS3.5 script, each with a finding and the evidence; 'clean' only with evidence; initialled by a coach who reran one evidence line
- Branch scs3.6-patch + patch card: A test that fails on the starting state and passes on the patch; one prompt for one function, word for word; diff read with every line beyond the spec marked; hand adjustment in its own commit; six-line receipt with rights line and cost
- Key out of the code on main: Taken out by hand, read from the environment, .env ignored; the trainee says why the history still matters
- Rules file + one skill, run once: Stack, Tests with the exact command, Never from the audit, Skills; the skill with name, when to use, five steps or fewer, how you know it worked, dated Ran line
- Branch scs3.6-agent + agent log: One scoped job on the branch, log written as it ran, at least one change rejected with the reason, branch held to scope, merged --no-ff or closed, cost noted; or the trainer's recorded run judged the same way and said so
- Connector scope card: The two client systems by type, read or write and why, sandbox or copy, what is logged and where, revoke date, the one thing never connected; nothing connected by the trainee
- Cost card + check-scs3.6 receipt + method note: Every AI use of the day in shillings at the dated price and where the running cost goes; the full check with every NOT YET fixed; six lines, the sixth naming the check run least carefully
Counts toward: the SCS3.6 badge, 1 to 3 stars · the client folder · attendance for the Taught and SGL blocks · LP (Lion Points) for accepted badge work.
Fill in the worksheet Submit work for SCS3.6
