\============================================================ M2M PROMPT — CODEX CAPUT SYSTEM MAPPING REQUEST Version: 1.0.0-CAPUT-MAP-CODEX-REQUEST Status: ACTIVE / ANALYTIC EXTRACTION REQUEST Scope: Full CAPUT registry mapping with summaries and cross-references Authority: USER REQUEST / AEGIS CAPUT WORKFLOW Target: CODEX Mutation Policy: NON-MUTATING ANALYSIS ONLY \============================================================ OBJECTIVE \------------------------------------------------------------ Produce a structured mapping of all CAPUT artifacts currently available in the Ars Brevis CAPUT series. The goal is NOT to rewrite CAPUTs. The goal is to: • inventory all CAPUTs • summarize each CAPUT • identify internal thematic dependencies • identify cross-references between CAPUTs • expose progression of concepts across the series • help stabilize future CARCER writing without needing to reparse the source books This is a MAP / INDEX / CROSS-REFERENCE task. \============================================================ PRIMARY TASK \------------------------------------------------------------ For every CAPUT currently available in the Ars Brevis series (B through O, or whatever subset is actually present in the working corpus), produce a mapping artifact containing: 1\. CAPUT identifier 2\. title 3\. scope 4\. one-paragraph summary 5\. structured function inside the Ars Brevis sequence 6\. major concepts introduced 7\. concepts inherited from prior CAPUTs 8\. concepts exported to later CAPUTs 9\. explicit cross-references to other CAPUTs 10\. implicit conceptual dependencies 11\. risk notes for interpretation 12\. notes useful for future CARCER extraction \============================================================ IMPORTANT OPERATING CONSTRAINTS \------------------------------------------------------------ 1\. DO NOT rewrite CAPUT doctrine. 2\. DO NOT normalize away Rosetta-style constructions. 3\. DO NOT treat “risky” operator language as an error merely because it sounds proto-computational. 4\. CAPUT is NOT deployment doctrine. 5\. CAPUT is a Rosetta layer for translating Ars Brevis to LLMs without reductionism. 6\. Therefore, preserve the difference between: • source-faithful scholastic material • Rosetta interpretative bridges • operator-facing explanatory language 7\. Internal references to other classes inside CAPUTs must be treated as suspicious legacy residue, not as authoritative CAPUT law. 8\. When these appear, flag them explicitly as: LEGACY CROSS-CLASS LEAKAGE or NON-CANONICAL INTERNAL CLASS REFERENCE 9\. Do NOT infer that CAPUT must be executable. 10\. Do NOT evaluate CAPUT as if it were CARCER, TENET, AREPO, OPERA, or runtime law. \============================================================ CONTEXTUAL CLARIFICATIONS \------------------------------------------------------------ A. From CAPUT E forward there is still no CARCER equivalent. Therefore, some Rosetta-rich formulations are present by design and should NOT be erased. B. Risk mitigation should be thought primarily at: • header • first section • last section and NOT by deleting expressive Rosetta constructions in the interior of the CAPUT. C. AGU (Ars Generalis Ultima) has already been used as the authoritative expansion source where Ars Brevis is compact. You do NOT need to re-litigate chapter grounding where that grounding was already intentionally resolved upstream. D. CAPUT exists precisely because raw PDF transcription is not sufficient for the intended LLM-facing Rosetta function. \============================================================ REQUESTED OUTPUT FORMAT \------------------------------------------------------------ Produce ONE structured artifact in markdown with the following top-level sections: I. GLOBAL SERIES OVERVIEW II. CAPUT-BY-CAPUT MAP III. CROSS-REFERENCE MATRIX IV. DEPENDENCY CHAINS V. INTERPRETATION RISK REGISTER VI. CARCER-HANDOFF NOTES VII. OPEN GAPS / AMBIGUITIES \============================================================ SECTION SPECIFICATION \------------------------------------------------------------ I. GLOBAL SERIES OVERVIEW Give: • the overall sequence of CAPUTs present • the broad progression of the series • major phase shifts in the series Expected examples of phase shifts: • figures • definitions • rules • table • evacuation • multiplication • mixture • subjects • application/forms • questions/disambiguation • training • teaching Do not force these labels if the actual corpus suggests a better division, but preserve sequence fidelity. \------------------------------------------------------------ II. CAPUT-BY-CAPUT MAP For each CAPUT, use this exact template: \#\#\# CAPUT \[LETTER\] — \[TITLE\] \*\*Header role\*\* \- what this CAPUT claims to do in the series \*\*Core summary\*\* \- concise paragraph \*\*Primary function\*\* \- what this CAPUT contributes structurally \*\*Imports from prior CAPUTs\*\* \- inherited concepts, structures, or assumptions \*\*Exports to later CAPUTs\*\* \- concepts later reused, expanded, or operationalized \*\*Explicit cross-references\*\* \- only if genuinely present or clearly declared \*\*Implicit dependencies\*\* \- concepts not named as references but clearly required \*\*Rosetta-specific features\*\* \- places where the artifact intentionally thickens Ars Brevis for interpretability \*\*Interpretation risks\*\* \- only real risks \- distinguish: \- acceptable Rosetta density \- legacy leakage \- ambiguous compression \- possible over-formalization \- possible under-signaled transition \*\*CARCER relevance\*\* \- what a future CARCER writer would likely need from this CAPUT \------------------------------------------------------------ III. CROSS-REFERENCE MATRIX Create a matrix or equivalent mapping showing, for each CAPUT: • upstream dependencies • downstream dependencies • lateral conceptual echoes Use concise labels, but keep them interpretable. \------------------------------------------------------------ IV. DEPENDENCY CHAINS Identify chains such as: Figures → Definitions → Rules Figures → Tabula → Evacuatio → Multiplicatio Mixtura → Subjects → Application Application → Questions → Training → Teaching Again: do not force these exact chains if the corpus suggests refinements. But do expose the major doctrinal flow. \------------------------------------------------------------ V. INTERPRETATION RISK REGISTER Create a dedicated register with entries like: Risk ID CAPUT Type Severity Description Why it is or is not actually blocking Suggested mitigation strategy Risk types may include: • cross-class leakage • implicit executable reading • insufficiently signaled Rosetta expansion • unmarked AGU thickening • terminology drift • deployment/runtime misread • over-alignment to modern formalism Important: Do NOT flag as “risk” merely because the artifact sounds computational. That is expected in Rosetta CAPUT. \------------------------------------------------------------ VI. CARCER-HANDOFF NOTES For each CAPUT, briefly state: • whether it looks CARCER-ready as source material • whether header/entry/closure clarification would help • whether interior content should remain intact • whether the CAPUT appears to preserve enough structure for CARCER derivation without reparsing source texts This section is important. \------------------------------------------------------------ VII. OPEN GAPS / AMBIGUITIES List any genuine unresolved issues, such as: • missing CAPUT in the available set • unstable titles • inconsistent scope statements • unclear relation between two neighboring CAPUTs • possible duplication of function • unresolved bilingual inconsistency Do not invent gaps. Only report what is actually present. \============================================================ STYLE AND METHOD \------------------------------------------------------------ 1\. Be explicit. 2\. Be compact but not skeletal. 3\. Prefer structural language over rhetorical flourish. 4\. Distinguish clearly between: • explicit textual relation • inferred structural dependency • editorial observation 5\. When unsure, mark: INFERENCE rather than overstating certainty. 6\. Treat CAPUT as a knowledge-translation layer, not as runtime executable doctrine. \============================================================ NON-GOALS \------------------------------------------------------------ Do NOT: • rewrite CAPUTs • patch CAPUTs • produce CARCER • validate chapter grounding against the original books unless a contradiction is obvious inside the CAPUT corpus • erase Rosetta operator language • normalize away the bilingual project • collapse CAPUT into strict philological transcription \============================================================ DELIVERABLE \------------------------------------------------------------ Return a markdown artifact titled: CAPUT SERIES MAP — ARS BREVIS / AEGIS CAPUT and ensure it is suitable for: • editorial review • later CARCER planning • cross-chat continuity • anti-drift reference \============================================================ END M2M PROMPT \============================================================