32 lines
1.3 KiB
Markdown
32 lines
1.3 KiB
Markdown
# Fable / Worker Onboarding Prompt - Leo / Teleo
|
|
|
|
current_canary: read the retained evidence index, then produce a repo/VPS/GCP/Telegram working-state map with exact claim ceilings and next executable action.
|
|
|
|
Use the Teleo repo skill pack at:
|
|
|
|
`.agents/skills/`
|
|
|
|
Load these draft skills first:
|
|
|
|
1. `skills/teleo-leo-onboarding/SKILL.md`
|
|
2. `skills/working-leo-m3taversal-outcomes/SKILL.md`
|
|
3. `skills/teleo-kb-db-change-workflow/SKILL.md`
|
|
4. `skills/teleo-vps-runtime-ops/SKILL.md`
|
|
5. `skills/teleo-proof-handoff/SKILL.md`
|
|
|
|
Hard constraints:
|
|
|
|
- Do not do paid route work or introduce paid-route naming.
|
|
- Do not change live VPS Leo runtime behavior unless explicitly told.
|
|
- Do not production-apply DB packets unless explicitly authorized.
|
|
- Live Telegram bot messages to the Leo group are allowed when they are test canaries for Leo behavior.
|
|
- Use Computer Use/Chrome for Telegram UI. Do not use AppleScript, OSA, System Events, or focus hijacking.
|
|
- If blocked, return `current_canary`, `attempted_routes`, `exact_gate`, `clear_CTA`, and `next_non_user_action`.
|
|
|
|
Expected output:
|
|
|
|
1. One-page understanding of the company/product/Leo role.
|
|
2. Current status split: VPS, Telegram, DB apply, GCP.
|
|
3. Exact list of evidence files read.
|
|
4. What is proven, not proven, and unsafe to claim.
|
|
5. Next action that can be run now without production mutation.
|