Use this portal to answer four questions before starting or reviewing work:
- Why does the company or product exist, and which principles constrain the solution?
- What is current fact, what is direction, and what remains unproven?
- Who owns the work and who made the durable decision?
- How should the product, interface, or publication behave?
Reading order
- Read governance to understand authority and the five functional responsibilities.
- Read the founder philosophy before choosing architecture or tooling.
- Use the product catalog to find the canonical public status page.
- Check the decision index before revisiting a settled trade-off.
- Apply the standards when writing, building, reviewing, or publishing.
- Use reports for verified outcomes and current risks.
Writing route
- Update product pages when stable requirements, boundaries, or status change.
- Add a decision record when a choice has lasting consequences or would be expensive to rediscover.
- Put verified outcomes in the next report; keep aspirations visibly labelled as future work.
- Keep raw exploration, private operations, credentials, personal data, and unpublished commercial context out of this public site.
A useful handoff
A reader should be able to identify the current state, the reason for the chosen direction, the accountable owner, the relevant interface, the evidence that was checked, and the next review trigger without needing the original conversation.