Submit Your Work
What You Turn In
- Your odoo-map.md (repo link)
- The five places with the real paths you found with your own commands, not the board's; they match odoo-look's receipt
- Your odoo-change-log.md (repo link)
- Faith made with the sales right only and watched logging in; Brian archived, never deleted; every action a row with how you checked it
- Your odoo-backup-log.md and one screenshot of the restored database on the known record
- The zip with the filestore, its three parts named; restored into a new name and the Upendo invoice found; restored again on a teammate's server; the zip itself stays in the evidence folder and on the stick
- Your odoo-tickets.md (repo link)
- Seven tickets and the interview ticket, each with what you saw — a screen, a record, a log line with its time; tickets 6 and 7 escalated with the five-part note
- Your odoo-runbook.md, and the team's client support runbook, change log and ticket log
- Six sections on one page, no password in it; the team's pages in the team's client folder, filed once, roles not names
- Your AI receipts and the support line of the team's honest answer
- Each ask with what you checked on the server; who would support the system and what that costs, at a published price checked on the day
- check-scs3.7 receipt and your method note
- Every NOT YET that is yours fixed; six lines, the sixth a real doubt; scs-server shut down, the checkpoint kept
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 next capstone stand-up.
Done when
- odoo-map.md, five real paths: Databases, filestore, config, log and service found by the trainee's own commands with the server's real paths; matches odoo-look's receipt
- odoo-change-log.md: One user made with the sales right only, first password in person, first log-in watched in a private window; Brian archived, not deleted; a row per action with how it was checked
- odoo-backup-log.md + restore screenshot: Zip with the filestore, three parts named; restored into a new database with the known record found; restored again on a teammate's server; dated. A backup only taken is a 1
- odoo-tickets.md: Seven tickets and the interview ticket, each with evidence seen (screen, record, log line with its time); 6 and 7 escalated with the five-part note; ticket 5 through the screens, never the database; 'fixed it' with nothing seen is not an entry
- odoo-runbook.md + the team's client runbook: Own: six sections, one page, paths from the map, last watched restore dated, no password. Team's: the client's demo database by role, the ladder, last three tickets, last restore dated or 'none watched'
- AI receipts + the support line: Every ask receipted with what was checked on the server; the support line names who supports the system and its cost at a published price checked on the day; the desk's own rate left empty until the rates sheet has an owner
- check-scs3.7 receipt + method note: Every NOT YET that is the trainee's fixed; six lines, the sixth a real doubt and a real check; scs-server shut down with the checkpoint kept
Counts toward: the SCS3.7 badge, 1 to 3 stars · the team's client folder · attendance for the briefing and the sprint blocks · LP (Lion Points) for accepted badge work.
Fill in the worksheet Submit work for SCS3.7
