Pitchpipe

Pitchpipe is where we write down how the platform actually works — and how we talk about it. Two jobs, mainly.

First, it’s the dictionary. Debt resolution is full of terms, codes, and internal shorthand that lives in people’s heads or buried in Forth, and every new person relearns it the hard way. Pitchpipe is where that vocabulary gets defined once, in plain language, so we’re all tuning to the same note.

Second, it’s the technical encyclopedia — how Foundation, Resonance, and the rest fit together, what talks to what, and why a thing works the way it does. Not just what a system does, but the reasoning behind it, so the knowledge doesn’t walk out the door when someone’s out or moves on.

There’s a third, forward-looking piece too. We’re actively working to move off Forth, and part of that work is being honest that Forth is legacy — so Pitchpipe is also where we sketch what the system could look like once we’re past it. That’s a living conversation, not a settled plan, and it belongs here in the open, not scattered across docs and DMs.

Where to start

• Glossary — the dictionary. Terms, codes, and the processes behind them.
• Architecture — the encyclopedia. The data model, how the systems fit together, and what we integrate with.
• Where We’re Headed — the post-Forth forward look.