# issues-fs.sgit.ai — Brief Pack

**Start with `00__BRIEF.md`.** Then `02__issues-fs-lite.md` and `04__what-ships.md` — those two are the site's reason to exist.

A brief pack for building `issues-fs.sgit.ai`, a new sibling on the sgit.ai network.

Prepared 22 August 2026 against [`owasp-sbot/Issues-FS__Docs`](https://github.com/owasp-sbot/Issues-FS__Docs), [`owasp-sbot/Issues-FS__Dev`](https://github.com/owasp-sbot/Issues-FS__Dev) (19 submodules), six module repos, and [`SGraph-AI__App__Send`](https://github.com/the-cyber-boardroom/SGraph-AI__App__Send) @ v0.33.62 — the flagship consumer, whose live `.issues/` graph is the best specimen in the ecosystem.

| File | What it gives you |
|---|---|
| `00__BRIEF.md` | **Read first.** The three jobs, the verified PyPI table, the thesis, real numbers, build order |
| `01__concepts-index.md` | 14 concept documents with paths, word counts and newcomer-readiness. Issues-FS is the **origin** of the estate's graph philosophy |
| `02__issues-fs-lite.md` | **The lite specification, extracted and publishable** — layout, task format, four operations, check-in cycle, lite-vs-full table |
| `03__the-data-model.md` | Nodes, edges, labels, the five regex primitives, on-disk layout — from code, not prose |
| `04__what-ships.md` | **The navigation deliverable.** 8 packages against live PyPI, 14 CLI commands with real flags, the three agent surfaces, the live graphs |
| `05__site-architecture.md` | Page-by-page IA with sources and publish status |
| `06__boundaries-and-house-style.md` | The graphs.sgit.ai boundary, the correction list, licensing, conventions |
| `07__gaps-and-open-questions.md` | Documented-not-built, built-not-documented, 7 open questions, 6 honest tensions |
| `08__source-manifest.csv` | **38 rows**, every path verified |

## Tiers

- **Tier 0 (18)** — publishable near-as-is, highest value
- **Tier 1 (14)** — publishable with correction, framing or a supersession note
- **Tier 2 (4)** — cite, don't republish (third-party imports, curiosities)
- **Tier 3 (2)** — do not publish (superseded, staging code)

## Verification

All 38 manifest paths verified. PyPI queried live and wheels unzipped. CLI commands verified against source. Node and edge counts measured by walking every `issue.json`. Test counts measured, not quoted — **the READMEs are wrong** (604 tests, not the 475 or 552 they claim).

## The three findings that shape the site

1. **Issues-FS-lite has no home.** The specification the commissioning brief calls "very important" lives in §7 of an 8,229-word manual about *email*, in a different repository. `02` extracts it, ready to publish.
2. **Two published PyPI packages are empty shells.** `issues-fs-service` and `issues-fs-service-client-python` ship 8-file wheels with no code, while their summaries promise a FastAPI server and a Python client.
3. **There is a third agent surface nobody has documented.** The `.issues` flat-file DSL — 11 source files, ~55 tests, 3 live examples, wired into the repository API, and **zero prose documentation anywhere**.

---

This document is released under the Creative Commons Attribution 4.0 International licence (CC BY 4.0).
