Contributors¶

This section is the onboarding board for people changing PackyTrace. It deliberately sits outside the final-report reading path: the material remains available without interrupting the academic architecture narrative.

Start here¶

1. Install the toolchain.
2. Run the platform.
3. Read the contribution workflow.
4. Use troubleshooting when the stack does not converge.

Learn the codebase¶

• Build phases explain how the product grew in working slices.
• Technology guides explain the selected backend, frontend, platform and tooling stack.
• Web application explains the frontend architecture.
• Usability audit records the product-facing review.

Practise before changing production code¶

The syntax and architecture exercises cover TypeScript, Go, Svelte, ports, dependency injection and placement decisions with examples drawn from PackyTrace.

Daily gates¶

• make check is the fast pre-PR gate.
• make ci adds builds and the full container journey test.
• make contracts-gen regenerates shared contract types after a JSON Schema change.
• The canonical domain model and current architecture reference override informal or older pages.