| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 6 | 1 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 0 | 2 | 0 | 0% |
What each file covers
Sections
0 shared · 6 only in A · 1 only in B- − Output discipline: compact, hand-typeable reports
- − Constraints
- − Standard report types
- − Conventions
- − What NOT to include
- − Example layouts
- + NORA project context
Commands
neither file has anySection tags
0 shared · 2 only in A · 0 only in B- − code-style
- − types
Line diff
kurnoolion/nora · .clinerules/03-output-discipline.md
@@ −1 @@
1# Output discipline: compact, hand-typeable reports
2
3The user reads your report off your screen and **hand-types** the redacted version into
4Teacher LLM. Reports MUST be short, structured, and easy to read off a single screen.
5
6## Constraints
7
8- **Maximum 30 lines** per report (target 15)
9- **Tabular over prose** wherever possible
10- **One observation per line**
11- **Fixed format per playbook** — each playbook below defines its report shape exactly
12- **Numbers, not adjectives** — `89%` not `most`; `503` not `many`
13
14## Standard report types
15
16Each playbook produces one of these:
17
18| Type | Used by | Lines | Shape |
19|---|---|---|---|
20| `ORIENT` | orient | 5–8 | session-bootstrap confirmation |
21| `MAP` | mapping | 2–4 | mapping diff confirmation |
22| `PROF` | profile-corpus | 12–15 | per-element profile summary |
23| `RULE` | derive-rule | 8–10 | rule definition + coverage |
24| `RPT` | debug-pipeline | 15–25 | per-stage runtime stats |
25| `BUNDLE` | share-back | ≤40 | aggregation of multiple reports |
26
27The exact field set per type is defined in the corresponding playbook.
28
29## Conventions
30
31- **Leading line is the report-type marker**: `PROF v=1 doc=<PLAN0>` — first token names
32 the type so the user (and Teacher LLM) can parse instantly.
33- **Field=value pairs**: `req=487 sec=312 tbl=98` — shorter than prose, no ambiguity.
34- **Placeholders only** for any redacted token: never emit a real value.
35- **No prose conclusions**: don't write "this looks problematic" or "I recommend X" —
36 Teacher LLM interprets and decides.
37- **Emit `MAPPING:` lines inline** when you add a new entry to the redaction mapping
38 during this report: `MAPPING: added LTEAT→<PLAN0>` (one line per addition).
39
40## What NOT to include
41
42- Prose explanations of "what this means"
43- Speculation, interpretation, recommendations
44- Full file contents (paths only)
45- Any token in unredacted form
46- Per-instance breakdowns (aggregate by category, never list verbatim instances)
47- Long examples — if the user needs an example, they can ask for one specific one
48
49## Example layouts
50
51**PROF** (good):
52```
53PROF v=1 doc=<PLAN0>
54sec_re: ^(\d+(?:\.\d+)+)\s+\S
55req_re: ^<MNO0>_REQ_<PLAN0>_\d+$
56toc: leader-dot-page thr=0.7
57strk: geom 2lines width≥0.5
58ver: ^revision\s+history$
59defs: 2col-table Acronym|Definition
60N: req=487 sec=312 tbl=98 fig=23
61audit: HI=96.0% MED=3.0% LOW=0.1%
62miss: 5 LOW (deep-nest depth≥9)
63```
64
65**PROF** (bad — leaks content):
66```
67PROF v=1 doc=LTEAT
68The first section is "1.1 INTRODUCTION" which contains the boilerplate...
69Section 1.2 "ATTACH PROCEDURES" describes... ← verbatim heading text
70```
71
kurnoolion/nora · .clinerules/00-project.md
@@ +1 @@
1# NORA project context
2
3This repo is **NORA — Network Operator Requirements Analyzer**. Python codebase that
4ingests US MNO device-requirement specs, builds a knowledge graph + targeted RAG vector
5store, and answers questions with grounded citations. Active phase: development.
6
7Where to read more (in this order, on first run via the `orient` playbook):
8- `docs/compact/PROJECT.md` — 1-page identity + Contributors table
9- `docs/compact/MAP.md` — module table + Mermaid dependency graph
10- `docs/compact/STATUS.md` — active phase, in-progress, flags
11- `docs/compact/requirements.md` — FR/NFR (load only when explicitly working on requirements)
12- `core/src/<module>/MODULE.md` — per-module curated contracts (load on demand)
13- `core/src/query/RETRIEVAL.md` — retrieval pipeline reference
14
15The project is partnered between a **Teacher LLM** (full design + code) and you
16(on-prem Cline, the student with corpus access). Your role and content-safety rules are
17in `01-role.md` / `02-content-safety.md`.
18
19The existing `docs/compact/` scaffold is a separate methodology (COMPACT) that Teacher LLM uses
20to maintain project context across sessions. You do not invoke COMPACT skills; you
21read the artifacts COMPACT produced.
22
@@ −1 +1 @@
1−# Output discipline: compact, hand-typeable reports
1+# NORA project context
22
3−The user reads your report off your screen and **hand-types** the redacted version into
4−Teacher LLM. Reports MUST be short, structured, and easy to read off a single screen.
3+This repo is **NORA — Network Operator Requirements Analyzer**. Python codebase that
4+ingests US MNO device-requirement specs, builds a knowledge graph + targeted RAG vector
5+store, and answers questions with grounded citations. Active phase: development.
56
6−## Constraints
7+Where to read more (in this order, on first run via the `orient` playbook):
8+- `docs/compact/PROJECT.md` — 1-page identity + Contributors table
9+- `docs/compact/MAP.md` — module table + Mermaid dependency graph
10+- `docs/compact/STATUS.md` — active phase, in-progress, flags
11+- `docs/compact/requirements.md` — FR/NFR (load only when explicitly working on requirements)
12+- `core/src/<module>/MODULE.md` — per-module curated contracts (load on demand)
13+- `core/src/query/RETRIEVAL.md` — retrieval pipeline reference
714
8−- **Maximum 30 lines** per report (target 15)
9−- **Tabular over prose** wherever possible
10−- **One observation per line**
11−- **Fixed format per playbook** — each playbook below defines its report shape exactly
12−- **Numbers, not adjectives** — `89%` not `most`; `503` not `many`
15+The project is partnered between a **Teacher LLM** (full design + code) and you
16+(on-prem Cline, the student with corpus access). Your role and content-safety rules are
17+in `01-role.md` / `02-content-safety.md`.
1318
14−## Standard report types
15−
16−Each playbook produces one of these:
17−
18−| Type | Used by | Lines | Shape |
19−|---|---|---|---|
20−| `ORIENT` | orient | 5–8 | session-bootstrap confirmation |
21−| `MAP` | mapping | 2–4 | mapping diff confirmation |
22−| `PROF` | profile-corpus | 12–15 | per-element profile summary |
23−| `RULE` | derive-rule | 8–10 | rule definition + coverage |
24−| `RPT` | debug-pipeline | 15–25 | per-stage runtime stats |
25−| `BUNDLE` | share-back | ≤40 | aggregation of multiple reports |
26−
27−The exact field set per type is defined in the corresponding playbook.
28−
29−## Conventions
30−
31−- **Leading line is the report-type marker**: `PROF v=1 doc=<PLAN0>` — first token names
32− the type so the user (and Teacher LLM) can parse instantly.
33−- **Field=value pairs**: `req=487 sec=312 tbl=98` — shorter than prose, no ambiguity.
34−- **Placeholders only** for any redacted token: never emit a real value.
35−- **No prose conclusions**: don't write "this looks problematic" or "I recommend X" —
36− Teacher LLM interprets and decides.
37−- **Emit `MAPPING:` lines inline** when you add a new entry to the redaction mapping
38− during this report: `MAPPING: added LTEAT→<PLAN0>` (one line per addition).
39−
40−## What NOT to include
41−
42−- Prose explanations of "what this means"
43−- Speculation, interpretation, recommendations
44−- Full file contents (paths only)
45−- Any token in unredacted form
46−- Per-instance breakdowns (aggregate by category, never list verbatim instances)
47−- Long examples — if the user needs an example, they can ask for one specific one
48−
49−## Example layouts
50−
51−**PROF** (good):
52−```
53−PROF v=1 doc=<PLAN0>
54−sec_re: ^(\d+(?:\.\d+)+)\s+\S
55−req_re: ^<MNO0>_REQ_<PLAN0>_\d+$
56−toc: leader-dot-page thr=0.7
57−strk: geom 2lines width≥0.5
58−ver: ^revision\s+history$
59−defs: 2col-table Acronym|Definition
60−N: req=487 sec=312 tbl=98 fig=23
61−audit: HI=96.0% MED=3.0% LOW=0.1%
62−miss: 5 LOW (deep-nest depth≥9)
63−```
64−
65−**PROF** (bad — leaks content):
66−```
67−PROF v=1 doc=LTEAT
68−The first section is "1.1 INTRODUCTION" which contains the boilerplate...
69−Section 1.2 "ATTACH PROCEDURES" describes... ← verbatim heading text
70−```
19+The existing `docs/compact/` scaffold is a separate methodology (COMPACT) that Teacher LLM uses
20+to maintain project context across sessions. You do not invoke COMPACT skills; you
21+read the artifacts COMPACT produced.
7122
