> ## Documentation Index
> Fetch the complete documentation index at: https://internal.softcrum.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Softcrum Suite — internal documentation

> The engineering source of truth: the constitution, the standards, the architecture decisions and the specification system that every module is built from.

These pages and the repository are the same files. An agent reads them from `docs/internal/`;
you read them rendered here. When the two disagree, the repository wins — so a documentation
change is part of the code change, never a follow-up.

<Columns cols={2}>
  <Card title="Foundations" icon="landmark" href="/constitution/overview">
    The rules that do not change without an amendment: the constitution, seven standards and
    twenty-two architecture decisions.
  </Card>

  <Card title="Modules" icon="cubes" href="/modules/overview">
    Five bounded contexts, each with a PRD, a living technical spec and its feature specs — the
    unit we actually deliver.
  </Card>

  <Card title="Execution" icon="rocket" href="/task-specs/overview">
    Task specs an agent works from, runbooks a human follows when something breaks, and the
    diagram specifications.
  </Card>

  <Card title="Design registry" icon="clipboard-list" href="/en/design/decision-registry-v1">
    Every closed decision with its `DEC-*` id, and the questions still open.
  </Card>

  <Card title="Legal" icon="scale-balanced" href="/en/legal/overview">
    Working drafts of the data-protection package. Unreviewed — a lawyer signs off before any
    of it leaves this site.
  </Card>

  <Card title="Glossary" icon="book" href="/glossary">
    The vocabulary this documentation assumes: tenant, contact, member, marketable contact.
  </Card>
</Columns>

## Where the work stands

|                        |                                                             |
| ---------------------- | ----------------------------------------------------------- |
| Modules decomposed     | 5 of 5 — identity, customer core, loyalty, messaging, CRM   |
| Feature specs written  | 51, plus 5 PRDs                                             |
| Specification status   | 41 `draft` · 15 `review` · **0 `approved`**                 |
| Architecture decisions | 22 ADRs, of which 8 are reconstructions awaiting validation |
| Open questions         | 70, grouped by who decides them                             |
| Application code       | none yet — it starts at TS-001                              |

The zero in that third row is the whole picture. Rule **R-S1** says no code merges for a feature
whose spec is not `approved`, and nothing is approved yet, so the specifications are not waiting
on more writing. They are waiting on decisions.

## What is blocked on the owner

<Steps>
  <Step title="Validate the founding constitution">
    Particularly [Part 2, the six port categories](/constitution/founding-constitution) — every
    line there is inferred, and TS-002 defines adapters against it. Confirming or correcting six
    lines now is cheap; doing it after the adapters exist is not.
  </Step>

  <Step title="Review amendment A1 line by line">
    It [adds two port categories](/constitution/amendment-A1-ports-and-standards) to a closed
    list, which is exactly the kind of change the constitution requires a human to make.
  </Step>

  <Step title="Answer group A of the open questions">
    [52 questions](/en/design/open-questions-v2), each with a recommendation. Answering them
    moves 37 specifications toward `approved`.
  </Step>

  <Step title="Sign off the fifteen loyalty documents in review">
    They sit at `0.2.0`. Approval is what makes them `1.0.0` and unblocks the first slice.
  </Step>
</Steps>

## How a decision reaches the code

```
DEC-*  ──►  ADR  ──►  PRD  ──►  Module spec  ──►  FS  ──►  TS (optional)  ──►  PR
 the        the       what      what exists      the      how the agent      links
 decision   why       and for   right now        unit of  executes it        back to
            behind it whom                       delivery                    the FS
```

Every link in that chain is checked in CI. A feature spec citing a `DEC-*` that does not exist
fails the build; a table in a module spec that no feature spec claims is reported as uncovered.
The mechanics are in [the specification system](/modules/overview).

<Note>
  This site is a mirror of a private repository and is not indexed. The Spanish version is a
  faithful translation of the same files: English is authoritative for engineering documents,
  Spanish for the legal package and the design registry.
</Note>