Tingg

h1. Tinggit Platform Wiki – Operating Model & Knowledge Architecture

*This page is the authoritative root of the Tinggit Platform Wiki.*

*It defines where every type of information must live — now and in the future.*

{{toc}}

---

h2. 1. Purpose of This Wiki

The Tinggit Platform Wiki is the **long-term memory and operating system** for how Tinggit works.

It exists to:

* Standardize how work is delivered

* Preserve sprint and release history

* Capture engineering standards

* Record decisions, risks, and opportunities

* Support audits, compliance, and scale

*bq.* If information is not placed in the correct section of this wiki, it is considered unofficial.

---

h2. 2. How to Use This Wiki (Very Important)

This wiki is **not a single document**.

It is a *structured system*.

Before creating or updating any page, ask:

* What type of information is this?

* Is it stable or sprint-specific?

* Does it define rules or describe usage?

* Will we need this information next year?

The answers determine *where it belongs*.

---

h2. 3. Wiki Architecture Overview (Single Source of Truth)

All wiki content must live under **one of the sections below**.

No exceptions.

---

h2. 4. Operating Model (HOW We Work – Authoritative Rules)

This section defines **mandatory rules** for how Tinggit delivers software.

These pages:

* Are authoritative

* Override all other pages

* Must not be duplicated

* Must not be reinterpreted

Pages in this section:

* [[Product Process Guidelines]]

* [[Sprint Open Process]]

* [[Sprint Execution Rules]]

* [[Sprint Close Process Guideline]]

* [[Sprint History, Metrics & Audit]]

* [[Release Management Process]]

* [[Edge Case & Exception Handling]]

*bq.* If there is a conflict, pages in this section always win.

---

h2. 5. Role-Based Guides (HOW to Follow the Rules)

This section explains **day-to-day usage** of the operating model.

These pages:

* Explain actions, not rules

* Never redefine process

* Always link back to Operating Model pages

Pages in this section:

* [[Product Owner Training Guide]]

* [[Sprint Team Training Guide]]

* [[QA & Compliance Training Guide]]

---

h2. 6. Engineering Standards (HOW We Build)

This section defines **technical and engineering standards** that apply across all products.

This section is for:

* Stable, long-lived standards

* “Must / Must not” technical rules

* Architecture and security principles

This section is NOT for:

* Tutorials

* Setup guides

* Sprint-specific implementation notes

* Temporary experiments

Pages in this section include:

* Coding Standards

* Architecture Principles

* API & Integration Guidelines

* Security & Compliance Practices

* Branching & PR Guidelines

---

h2. 7. Product & Business Context (WHY We Build)

This section captures **product intent and business boundaries**.

These pages:

* Explain *why* work exists

* Do NOT track execution

* Do NOT replace backlog items

Pages in this section:

* [[Tingg Insight Business Requirements Document ]]

* [[Tingg Insight HIPAA Compliance Scope and Applicability]]

* Product Vision & Goals

* Product Roadmap (High-Level)

---

h2. 8. Decision, Risk & Opportunity Register (WHY Choices Were Made)

This section preserves **strategic memory**.

It answers:

* Why a decision was taken

* What risks were accepted

* What opportunities were identified

Pages in this section:

* Key Decisions (ADR-lite)

* Risk Register

* Opportunity Register

These pages prevent:

* Loss of context

* Repeated mistakes

* Hindsight bias

---

h2. 9. Sprint Records (HISTORICAL – Read Only)

This section stores **sprint-level historical summaries**.

Each sprint may have ONE wiki page.

Structure:

<pre>

Sprint Records

├── Sprint YYYY-NN

</pre>

Sprint wiki pages may contain:

* Sprint Goal

* Outcome summary

* Final velocity

* Spillover summary

* Retrospective action items (linked issues)

Sprint wiki pages must NOT contain:

* Task tracking

* Daily updates

* Status changes

* Rewritten metrics

*bq.* Sprint execution lives in issues, not in wiki.

---

h2. 10. Reference & Templates (Reusable Assets)

This section contains **reusable templates and stable references**.

Structure:

<pre>

Reference & Templates

├── Templates

│   ├── Sprint Wiki Template

│   ├── Risk Entry Template

│   ├── Decision Record Template

│   └── Release Notes Template

└── Glossary & External Links

</pre>

Templates are tools — not content.

---

h2. 11. Governance Rules (Mandatory)

To keep this wiki reliable and scalable:

* Every page must belong to exactly one section

* No sprint-specific tracking outside Sprint Records

* No process duplication

* No temporary content in wiki

* No rewriting of sprint or release history

Violations create confusion and destroy trust.

---

h2. 12. Golden Placement Rule (Memorize This)

*bq.* If information changes sprint-to-sprint → it belongs in issues.  

*bq.* If information must be remembered next year → it belongs in wiki.

---

h2. 13. Final Statement

This wiki is not documentation for documentation’s sake.

It is the **operating backbone of the Tinggit Platform** —

designed to scale people, products, decisions, and compliance

without chaos.

Start here.

Place information correctly.

Do not improvise.