ghost

Read all project markdown documents and examine the codebase to ground in the project's actual state.

Ghost Dependency Audit

Systematically surface the invisible substrate:

1. Environment assumptions — Variables read but not documented, config files expected but not templated, paths assumed to exist, permissions required but unspecified.
2. Service dependencies — External services called without explicit documentation. DNS entries assumed. Ports expected to be open. Health checks missing.
3. Timing assumptions — Operations that assume ordering but don't enforce it. Race conditions waiting to happen. Startup sequences that depend on undocumented timing.
4. Implicit contracts — Module boundaries where the interface is convention rather than code. Data formats assumed but not validated. Error handling that assumes specific upstream behavior.
5. Build & deploy assumptions — Tools expected to be installed. Versions assumed. Build order dependencies. Network access during build.
6. Data assumptions — Seed data expected. Migration order dependencies. Schema assumptions not enforced by constraints. Encoding assumptions.
7. Human assumptions — Knowledge required but not documented. Procedures that exist only in someone's head. Tribal knowledge.

Focus area: $ARGUMENTS

For every ghost dependency found:

1. What the assumption is (specific)
2. Where it lives in the code or process
3. What happens when the assumption is violated
4. How to make it explicit (document, validate, or enforce)

Present as an action list. No changes to files — document only.

Output

Order findings by "what breaks at 2am" severity. State the total count when complete.

What questions would I benefit from asking?

What am I not asking?