Code Guidance

This corpus works best when each file reads like lived experience, not notes for later.

What good source material looks like

• First-person experience with concrete context.
• Clear decisions, tradeoffs, and outcomes.
• Specific metrics, constraints, or failure modes when you have them.
• Language that sounds like Justin, not generic management advice.

What to avoid

• Templates, placeholders, and TODO-style notes.
• Topic stubs with no real examples.
• Long files that mix unrelated subjects.
• Internal authoring docs meant for humans writing the corpus.

Preferred file shape

• One topic per file.
• Start with a clear # title.
• Group by sections such as context, approach, tradeoffs, outcomes, and what you would do differently.
• Keep sections cohesive so chunking produces focused retrieval units.

Feedback loop

Run:

./scripts/build-index.sh

This writes indexing/corpus_feedback.json.

Interpretation:

• failures: content that should not be embedded until fixed.
• warnings: thin material that is valid but may not ground answers strongly.

Strong additions to prioritize

• Real incidents with timeline, decision points, and recovery tradeoffs.
• Performance management situations with signals, action, and outcome.
• Architecture choices with why one option was rejected.
• Hiring and organizational calls with concrete constraints.