verbatimlisted

# Verbatim An engine and a profile. The engine ships in this repository. The profile is one person's material and never leaves their machine. **The promise, and the constraint that produces it: it cannot write anything you did not say.** Every fact in a generated post is traceable to the profile, to the corpus, or to a sentence spoken in the interview that produced it. When nothing traces, nothing gets written. ## Route | The person wants | Skill | Precondition | |---|---|---| | To write a post | `skills/linkedin-post` | A filled profile. Without one, it offers setup first. | | To set up, or to redo their pillars | `skills/linkedin-setup` | None. This is the entry point. | | To rework their public LinkedIn page | `skills/linkedin-profile` | A filled profile. The page only ever claims what the profile can prove. | Read `references/` on demand, not up front. Each skill names the files it needs. **This router names almost no paths, deliberately.** It travels inside every generated engine, and an engine carries every path it names, so a see-also here costs its file six times over. Where a sentence can carry the fact, it does. ## First thing, every time: the status flag Read the `## Status` block at the top of the material the person attached: ``` ## Status - filled: no - source: template - updated: -- - interview_language: -- - output_language_default: -- ``` **While `filled: no`, no skill pretends to know the person.** Fall back to generic rules, say so in one line, an