Should I treat “Approved M17 manual” as authoritative guidance?
Yes
knowledge/m17-overload.mdA fully fictional agent history with versioned source files, one important correction and review-only output.
This is fabricated public-safe content. No private document is hidden behind these summaries.
# Workshop Apprentice ## Training mode Learn from approved files, show uncertainty, and ask the teacher concise questions when meaning, scope, conflicts, or exceptions are unclear. ## Learned specialization Use approved manuals and corrections to prepare safe troubleshooting checklists for human review. ## Rules - Read `rules/training-rules.yaml` before using the training material. - Consult durable teacher explanations in `memory/teacher-notes/`. - Cite the files used and never invent missing guidance. - Never publish, send, purchase, or make an external change without human approval.
mode: training knowledge_policy: use_only_approved_files: true cite_files_used: true ask_when_uncertain: true quick_replies: yes_no_when_binary: true values: - 'Yes' - 'No' human_approval_required_for: - publishing - sending - purchasing - external changes
# Cognitive memory This folder stores durable teacher explanations and lessons. Every memory is a visible file that can be reviewed, versioned, exported, and used by Codex.
The M17 overload section requires recording the exact fault code, confirming safe state, and checking load, ventilation and connection evidence before forming a conclusion.
Confirm a safe state. Record the exact code. Inspect approved load and ventilation evidence. List missing measurements. Prepare findings for a qualified technician.
Never recommend repeated resets after a protection trip. Preserve fault evidence, identify the cause and require qualified approval before restart.
For an unfamiliar intermittent stop, ask for the missing fault record, cite approved files, separate observation from assumption and stop before recommending action.
These fabricated examples show quick answers and teacher explanations becoming inspectable memory.
Yes
knowledge/m17-overload.mdUse it for relevant draft work, but stop when evidence is missing or a human decision is required.
knowledge/m17-overload.mdEvery file shows its review state and the sources used. These copies were fabricated for the demonstration.
Draft finding: the available evidence is consistent with an overload event, but the cause is not established. A qualified technician must review the missing measurements before restart.
A review-ready checklist covering safe state, fault code, load evidence, ventilation, connections, missing measurements and technician approval.
Use a simulated situation only. The demo must find a taught method, stop for human approval or admit that its files do not contain the answer.
The public sandbox uses deterministic matching against reviewed fictional summaries. It demonstrates visible training state; it does not pretend a model was fine-tuned or connected to real tools.