any2md 1.0.6__tar.gz → 1.0.7__tar.gz

{any2md-1.0.6 → any2md-1.0.7}/CHANGELOG.md

@@ -4,6 +4,36 @@ All notable changes to this project will be documented in this file.
 
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
+## [1.0.7] — 2026-04-29
+
+Branding/rebrand release. The frontmatter contract that any2md emits is
+now described as "SAGE-compatible" (Security Analysis and Guidance
+Exchange) — the upstream specification was renamed from SSRM (Structured
+Security Reasoning Markdown) to SAGE. No functional or schema changes:
+field names, ordering, controlled vocabularies, and `content_hash`
+derivation are byte-identical to v1.0.6. Existing v1.0.6 outputs remain
+valid SAGE-compatible documents without modification.
+
+### Changed
+
+- README, CHANGELOG, and all of `docs/` updated to reference SAGE /
+  Security Analysis and Guidance Exchange.
+- `--auto-id` CLI help text now reads "SAGE-conformant document_id"
+  (previously "SSRM-conformant"). Behavior unchanged.
+- Module/function docstrings in `any2md/frontmatter.py`,
+  `any2md/converters/txt.py`, and `any2md/pipeline/cleanup.py` updated
+  to reference SAGE §3 / §5.1 (same section numbers as the upstream
+  SSRM v1.0-RC1 spec).
+- Two test functions renamed for naming consistency
+  (`test_txt_end_to_end_writes_sage_compat_output`,
+  `test_compose_emits_required_sage_fields`). Pytest auto-discovery is
+  unaffected; assertions unchanged.
+
+### Migration
+
+None required. Public API, CLI flags, frontmatter shape, and
+`content_hash` outputs are all preserved bit-for-bit.
+
 ## [1.0.6] — 2026-04-27
 
 Security hardening release. Closes 8 actionable findings from the
@@ -318,7 +348,7 @@ Patch release. Adds an explicit backend-selection CLI flag.
 First stable release of any2md v1.0. Validated end-to-end against
 real-world documents (a 164-page PDF technical standard via Docling,
 a multi-page academic DOCX, and a Wikipedia article via trafilatura).
-The output contract — SSRM-compatible frontmatter, deterministic
+The output contract — SAGE-compatible frontmatter, deterministic
 `content_hash`, NFC + LF body normalization — is now stable. Downstream
 consumers can rely on this shape.
 
@@ -340,7 +370,7 @@ Phase 4: configuration, polish, and the v1.0 documentation set.
 - `--meta-file PATH` flag plus auto-discovery of `.any2md.toml` (walks up
   from cwd). The `[meta]` table supplies frontmatter overrides; the
   `[document_id]` table supplies `--auto-id` prefix and type code.
-- `--auto-id` flag — generates an SSRM-conformant `document_id` as
+- `--auto-id` flag — generates an SAGE-conformant `document_id` as
   `{PREFIX}-{YYYY}-{TYPE}-{SHA8}`. Defaults to `LOCAL`/`DOC`; override via
   the `[document_id]` table in `.any2md.toml`.
 - `--strict` flag — promotes pipeline validation warnings (heading
@@ -359,7 +389,7 @@ Phase 4: configuration, polish, and the v1.0 documentation set.
 - Comprehensive documentation set:
   - `README.md` rewritten with educational tone — every command preceded
     by why you'd run it and followed by what you'll see.
-  - `docs/output-format.md` — SSRM-compatible field reference and the
+  - `docs/output-format.md` — SAGE-compatible field reference and the
     `content_hash` recomputation recipe.
   - `docs/cli-reference.md` — flag-by-flag reference with use cases and a
     worked-example matrix.
@@ -462,14 +492,14 @@ any2md transparently falls back to pymupdf4llm (PDF) and mammoth (DOCX).
 
 First prerelease of any2md v1.0. Phase 1 of 5: foundation only — no Docling
 backend yet, no new CLI flags. Output frontmatter has been rewritten to be
-SSRM-compatible (Structured Security Reasoning Markdown) — this is a
+SAGE-compatible (Security Analysis and Guidance Exchange) — this is a
 breaking change for downstream consumers parsing v0.7 output. See
 `docs/superpowers/specs/2026-04-26-any2md-v1-design.md` for the full
 v1.0 design and `docs/superpowers/plans/2026-04-26-any2md-v1-phase1-foundation.md`
 for this phase's task plan.
 
 ### Added
-- New `any2md/frontmatter.py` module — SSRM-compatible YAML emitter with the
+- New `any2md/frontmatter.py` module — SAGE-compatible YAML emitter with the
   `SourceMeta` dataclass, deterministic `compute_content_hash`,
   `estimate_tokens`, `recommend_chunk_level`, `extract_abstract`, and
   `derive_title` helpers, plus the central `compose()` function (the only
@@ -495,7 +525,7 @@ for this phase's task plan.
   `reportlab`, `ruff`.
 
 ### Changed
-- **BREAKING:** Output frontmatter shape is now SSRM-compatible. New required
+- **BREAKING:** Output frontmatter shape is now SAGE-compatible. New required
   fields: `document_id` (empty string by default — opt-in via future
   `--auto-id`), `version`, `date`, `status: "draft"`, `document_type` (empty
   for non-security documents), `content_domain` (empty array),

{any2md-1.0.6 → any2md-1.0.7}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: any2md
-Version: 1.0.6
+Version: 1.0.7
 Summary: Convert PDF, DOCX, HTML, and TXT files — or web pages by URL — to clean, LLM-optimized Markdown with YAML frontmatter.
 Project-URL: Homepage, https://github.com/rocklambros/any2md
 Project-URL: Issues, https://github.com/rocklambros/any2md/issues
@@ -52,7 +52,7 @@ The full design rationale lives in [docs/superpowers/specs/2026-04-26-v1.0.3-emp
 
 ## What this is
 
-any2md ingests heterogeneous source documents and emits Markdown with a fixed YAML frontmatter contract. The frontmatter shape is SSRM-compatible (Structured Security Reasoning Markdown — a documented schema for LLM-consumable documents), so retrieval pipelines, embeddings jobs, and chunking utilities downstream can rely on field names, types, and a deterministic `content_hash` for cache invalidation. The body is NFC-normalized with LF line endings, and the heading hierarchy is guaranteed to start at H1 and not skip levels. The goal is one stable shape, regardless of whether a document started life as a scanned PDF, a Word doc, a Wikipedia page, or a plain text dump.
+any2md ingests heterogeneous source documents and emits Markdown with a fixed YAML frontmatter contract. The frontmatter shape is SAGE-compatible (Security Analysis and Guidance Exchange — a documented schema for LLM-consumable documents), so retrieval pipelines, embeddings jobs, and chunking utilities downstream can rely on field names, types, and a deterministic `content_hash` for cache invalidation. The body is NFC-normalized with LF line endings, and the heading hierarchy is guaranteed to start at H1 and not skip levels. The goal is one stable shape, regardless of whether a document started life as a scanned PDF, a Word doc, a Wikipedia page, or a plain text dump.
 
 ## Quick start
 
@@ -144,8 +144,8 @@ document_id: ""                                    # empty unless you pass --aut
 version: "1"                                       # "1" for source files without an embedded version
 date: "2026-03-15"                                 # docx core props "modified" → ISO-8601
 status: "draft"                                    # always "draft" for converted documents
-document_type: ""                                  # SSRM controlled vocab — empty for non-security docs
-content_domain: []                                 # SSRM controlled vocab — empty array when unknown
+document_type: ""                                  # SAGE controlled vocab — empty for non-security docs
+content_domain: []                                 # SAGE controlled vocab — empty array when unknown
 authors:                                           # extracted from docProps/core.xml dc:creator
   - "Rock Lambros"
 organization: ""                                   # docProps/app.xml Company; empty when absent
@@ -166,7 +166,7 @@ produced_by: "Microsoft® Word for Microsoft 365"   # software that produced the
 ---
 ```
 
-Fields under `# any2md extension field` are retained from v0.7 for traceability and observability — they're not part of the SSRM contract proper, but they live in the same frontmatter block. See [docs/output-format.md](docs/output-format.md) for the full field reference.
+Fields under `# any2md extension field` are retained from v0.7 for traceability and observability — they're not part of the SAGE contract proper, but they live in the same frontmatter block. See [docs/output-format.md](docs/output-format.md) for the full field reference.
 
 ### Before / after
 
@@ -362,7 +362,7 @@ You'll see the OK lines as if the conversion were fresh; previously-written outp
 
 ## The output format
 
-Every file converted by any2md has the same frontmatter shape, regardless of source format. The shape is **SSRM-compatible** — it matches the field names, types, and ordering of the Structured Security Reasoning Markdown specification, but values aren't required to match SSRM's controlled vocabularies (most converted documents aren't security research). Fields that require a controlled vocabulary (`document_type`, `content_domain`, `tlp`) are emitted empty unless you supply them via `--meta` or `.any2md.toml`.
+Every file converted by any2md has the same frontmatter shape, regardless of source format. The shape is **SAGE-compatible** — it matches the field names, types, and ordering of the Security Analysis and Guidance Exchange specification, but values aren't required to match SAGE's controlled vocabularies (most converted documents aren't security research). Fields that require a controlled vocabulary (`document_type`, `content_domain`, `tlp`) are emitted empty unless you supply them via `--meta` or `.any2md.toml`.
 
 ### Field auto-fill summary
 
@@ -407,7 +407,7 @@ You'll see the OK line as usual. The frontmatter of `Text/paper.md` will have `o
 
 ### `.any2md.toml`
 
-You'd use this when you have a stable set of frontmatter defaults that should apply to every conversion in a project. The file is auto-discovered by walking up from the current working directory, so you can drop one at the root of your corpus repo and forget about it. Worked example for a security-research org producing SSRM-conforming outputs:
+You'd use this when you have a stable set of frontmatter defaults that should apply to every conversion in a project. The file is auto-discovered by walking up from the current working directory, so you can drop one at the root of your corpus repo and forget about it. Worked example for a security-research org producing SAGE-conforming outputs:
 
 ```toml
 [meta]
@@ -561,7 +561,7 @@ The two-lane design exists because Docling output is layout-correct (running agg
 
 ## Migrating from v0.7
 
-v1.0 emits SSRM-compatible frontmatter — that's the one intended breaking change. v0.7's small frontmatter (`title`, `source_file`, `pages`, `type`, `word_count`) becomes a fuller block with `document_id`, `version`, `date`, `status`, `content_hash`, `token_estimate`, `authors`, and several other fields. The v0.7 fields are retained as any2md extension fields in the same block, so traceability is preserved, but downstream parsers that expected the old fixed shape will need to update. The body is now NFC-normalized with LF line endings, which means `content_hash` is reproducible. If you need bit-for-bit v0.7 output, pin `any2md==0.7.0`. The full field-by-field migration guide and behavior-change list lives in [docs/upgrading-from-0.7.md](docs/upgrading-from-0.7.md).
+v1.0 emits SAGE-compatible frontmatter — that's the one intended breaking change. v0.7's small frontmatter (`title`, `source_file`, `pages`, `type`, `word_count`) becomes a fuller block with `document_id`, `version`, `date`, `status`, `content_hash`, `token_estimate`, `authors`, and several other fields. The v0.7 fields are retained as any2md extension fields in the same block, so traceability is preserved, but downstream parsers that expected the old fixed shape will need to update. The body is now NFC-normalized with LF line endings, which means `content_hash` is reproducible. If you need bit-for-bit v0.7 output, pin `any2md==0.7.0`. The full field-by-field migration guide and behavior-change list lives in [docs/upgrading-from-0.7.md](docs/upgrading-from-0.7.md).
 
 ## Security
 

{any2md-1.0.6 → any2md-1.0.7}/README.md

@@ -19,7 +19,7 @@ The full design rationale lives in [docs/superpowers/specs/2026-04-26-v1.0.3-emp
 
 ## What this is
 
-any2md ingests heterogeneous source documents and emits Markdown with a fixed YAML frontmatter contract. The frontmatter shape is SSRM-compatible (Structured Security Reasoning Markdown — a documented schema for LLM-consumable documents), so retrieval pipelines, embeddings jobs, and chunking utilities downstream can rely on field names, types, and a deterministic `content_hash` for cache invalidation. The body is NFC-normalized with LF line endings, and the heading hierarchy is guaranteed to start at H1 and not skip levels. The goal is one stable shape, regardless of whether a document started life as a scanned PDF, a Word doc, a Wikipedia page, or a plain text dump.
+any2md ingests heterogeneous source documents and emits Markdown with a fixed YAML frontmatter contract. The frontmatter shape is SAGE-compatible (Security Analysis and Guidance Exchange — a documented schema for LLM-consumable documents), so retrieval pipelines, embeddings jobs, and chunking utilities downstream can rely on field names, types, and a deterministic `content_hash` for cache invalidation. The body is NFC-normalized with LF line endings, and the heading hierarchy is guaranteed to start at H1 and not skip levels. The goal is one stable shape, regardless of whether a document started life as a scanned PDF, a Word doc, a Wikipedia page, or a plain text dump.
 
 ## Quick start
 
@@ -111,8 +111,8 @@ document_id: ""                                    # empty unless you pass --aut
 version: "1"                                       # "1" for source files without an embedded version
 date: "2026-03-15"                                 # docx core props "modified" → ISO-8601
 status: "draft"                                    # always "draft" for converted documents
-document_type: ""                                  # SSRM controlled vocab — empty for non-security docs
-content_domain: []                                 # SSRM controlled vocab — empty array when unknown
+document_type: ""                                  # SAGE controlled vocab — empty for non-security docs
+content_domain: []                                 # SAGE controlled vocab — empty array when unknown
 authors:                                           # extracted from docProps/core.xml dc:creator
   - "Rock Lambros"
 organization: ""                                   # docProps/app.xml Company; empty when absent
@@ -133,7 +133,7 @@ produced_by: "Microsoft® Word for Microsoft 365"   # software that produced the
 ---
 ```
 
-Fields under `# any2md extension field` are retained from v0.7 for traceability and observability — they're not part of the SSRM contract proper, but they live in the same frontmatter block. See [docs/output-format.md](docs/output-format.md) for the full field reference.
+Fields under `# any2md extension field` are retained from v0.7 for traceability and observability — they're not part of the SAGE contract proper, but they live in the same frontmatter block. See [docs/output-format.md](docs/output-format.md) for the full field reference.
 
 ### Before / after
 
@@ -329,7 +329,7 @@ You'll see the OK lines as if the conversion were fresh; previously-written outp
 
 ## The output format
 
-Every file converted by any2md has the same frontmatter shape, regardless of source format. The shape is **SSRM-compatible** — it matches the field names, types, and ordering of the Structured Security Reasoning Markdown specification, but values aren't required to match SSRM's controlled vocabularies (most converted documents aren't security research). Fields that require a controlled vocabulary (`document_type`, `content_domain`, `tlp`) are emitted empty unless you supply them via `--meta` or `.any2md.toml`.
+Every file converted by any2md has the same frontmatter shape, regardless of source format. The shape is **SAGE-compatible** — it matches the field names, types, and ordering of the Security Analysis and Guidance Exchange specification, but values aren't required to match SAGE's controlled vocabularies (most converted documents aren't security research). Fields that require a controlled vocabulary (`document_type`, `content_domain`, `tlp`) are emitted empty unless you supply them via `--meta` or `.any2md.toml`.
 
 ### Field auto-fill summary
 
@@ -374,7 +374,7 @@ You'll see the OK line as usual. The frontmatter of `Text/paper.md` will have `o
 
 ### `.any2md.toml`
 
-You'd use this when you have a stable set of frontmatter defaults that should apply to every conversion in a project. The file is auto-discovered by walking up from the current working directory, so you can drop one at the root of your corpus repo and forget about it. Worked example for a security-research org producing SSRM-conforming outputs:
+You'd use this when you have a stable set of frontmatter defaults that should apply to every conversion in a project. The file is auto-discovered by walking up from the current working directory, so you can drop one at the root of your corpus repo and forget about it. Worked example for a security-research org producing SAGE-conforming outputs:
 
 ```toml
 [meta]
@@ -528,7 +528,7 @@ The two-lane design exists because Docling output is layout-correct (running agg
 
 ## Migrating from v0.7
 
-v1.0 emits SSRM-compatible frontmatter — that's the one intended breaking change. v0.7's small frontmatter (`title`, `source_file`, `pages`, `type`, `word_count`) becomes a fuller block with `document_id`, `version`, `date`, `status`, `content_hash`, `token_estimate`, `authors`, and several other fields. The v0.7 fields are retained as any2md extension fields in the same block, so traceability is preserved, but downstream parsers that expected the old fixed shape will need to update. The body is now NFC-normalized with LF line endings, which means `content_hash` is reproducible. If you need bit-for-bit v0.7 output, pin `any2md==0.7.0`. The full field-by-field migration guide and behavior-change list lives in [docs/upgrading-from-0.7.md](docs/upgrading-from-0.7.md).
+v1.0 emits SAGE-compatible frontmatter — that's the one intended breaking change. v0.7's small frontmatter (`title`, `source_file`, `pages`, `type`, `word_count`) becomes a fuller block with `document_id`, `version`, `date`, `status`, `content_hash`, `token_estimate`, `authors`, and several other fields. The v0.7 fields are retained as any2md extension fields in the same block, so traceability is preserved, but downstream parsers that expected the old fixed shape will need to update. The body is now NFC-normalized with LF line endings, which means `content_hash` is reproducible. If you need bit-for-bit v0.7 output, pin `any2md==0.7.0`. The full field-by-field migration guide and behavior-change list lives in [docs/upgrading-from-0.7.md](docs/upgrading-from-0.7.md).
 
 ## Security
 

{any2md-1.0.6 → any2md-1.0.7}/any2md/__init__.py

@@ -1,3 +1,3 @@
 """Convert PDF, DOCX, HTML, and TXT files to LLM-optimized Markdown."""
 
-__version__ = "1.0.6"
+__version__ = "1.0.7"

{any2md-1.0.6 → any2md-1.0.7}/any2md/cli.py

@@ -200,7 +200,7 @@ def main():
     parser.add_argument(
         "--auto-id",
         action="store_true",
-        help="Generate an SSRM-conformant document_id of the form "
+        help="Generate an SAGE-conformant document_id of the form "
         "{PREFIX}-{YYYY}-{TYPE}-{SHA8}. Defaults: PREFIX=LOCAL, TYPE=DOC. "
         "Override via .any2md.toml [document_id] (publisher_prefix, type_code).",
     )

{any2md-1.0.6 → any2md-1.0.7}/any2md/converters/txt.py

@@ -176,7 +176,7 @@ def convert_txt(
     force: bool = False,
     strip_links_flag: bool = False,
 ) -> bool:
-    """Convert a plain-text file to v1.0 SSRM-compatible Markdown."""
+    """Convert a plain-text file to v1.0 SAGE-compatible Markdown."""
     if options is None:
         options = PipelineOptions(strip_links=strip_links_flag)
 

{any2md-1.0.6 → any2md-1.0.7}/any2md/frontmatter.py

@@ -1,4 +1,4 @@
-"""SSRM-compatible YAML frontmatter emitter.
+"""SAGE-compatible YAML frontmatter emitter.
 
 See spec §3 (frontmatter contract) and §5.0 (SourceMeta dataclass).
 This module is the single producer of the YAML block — converters
@@ -60,7 +60,7 @@ def filter_reserved_overrides(
 
 
 def compute_content_hash(body: str) -> str:
-    """SHA-256 of NFC-normalized, LF-line-ended body. SSRM §5.1.
+    """SHA-256 of NFC-normalized, LF-line-ended body. SAGE §5.1.
 
     The body MUST be the post-pipeline output (after C1-C5). This function
     re-applies NFC and LF normalization defensively so callers can pass any
@@ -74,7 +74,7 @@ def compute_content_hash(body: str) -> str:
 def generate_document_id(
     body: str, prefix: str = "LOCAL", type_code: str = "DOC"
 ) -> str:
-    """Generate an SSRM-conformant ``document_id`` from body content.
+    """Generate an SAGE-conformant ``document_id`` from body content.
 
     Pattern: ``{PREFIX}-{YYYY}-{TYPE}-{SHA8}``.
 
@@ -227,7 +227,7 @@ def _normalize_body(body: str) -> str:
 def _build_fields(
     body: str, meta: SourceMeta, options: PipelineOptions
 ) -> dict[str, Any]:
-    """Build the ordered field map for the SSRM frontmatter block.
+    """Build the ordered field map for the SAGE frontmatter block.
 
     Returns an insertion-ordered dict matching spec §3.2-3.4. Only fields
     that should be emitted are present; conditional fields (e.g. ``pages``,
@@ -333,7 +333,7 @@ def _emit_field(key: str, value: Any, lines: list[str]) -> None:
             lines.append(f"  {subkey}: {_emit_value(subval)}")
         return
     if isinstance(value, list):
-        # Only string-lists are supported for now (matches SSRM §3 fields).
+        # Only string-lists are supported for now (matches SAGE §3 fields).
         lines.append(f"{key}: {_emit_array([str(v) for v in value])}")
         return
     if isinstance(value, (int, float)) and not isinstance(value, bool):
@@ -359,7 +359,7 @@ def compose(
     options: PipelineOptions,
     overrides: dict[str, Any] | None = None,
 ) -> str:
-    """Build a complete SSRM-compatible Markdown document.
+    """Build a complete SAGE-compatible Markdown document.
 
     Steps:
     1. Normalize body to NFC + LF endings (matches content_hash invariant).

{any2md-1.0.6 → any2md-1.0.7}/any2md/pipeline/cleanup.py

@@ -14,7 +14,7 @@ Stage = Callable[[str, "PipelineOptions"], str]
 
 
 def nfc_normalize(text: str, _options: "PipelineOptions") -> str:
-    """C1: NFC unicode normalization. Required by SSRM §5.1 for content_hash."""
+    """C1: NFC unicode normalization. Required by SAGE §5.1 for content_hash."""
     return unicodedata.normalize("NFC", text)
 
 

{any2md-1.0.6 → any2md-1.0.7}/docs/architecture.md

@@ -167,7 +167,7 @@ normalizations that any well-formed markdown can absorb without harm:
 Centralizing these means `content_hash` is byte-deterministic: the same
 post-cleanup body produces the same hash regardless of which lane ran first,
 because the cleanup is the last thing that touched the bytes. This is the
-determinism boundary the SSRM contract relies on.
+determinism boundary the SAGE contract relies on.
 
 ## Stage catalog
 
@@ -244,7 +244,7 @@ order.
 
 | Run order | ID | Name | Lane | Input shape | Output shape | No-op cases | Edge cases |
 |---|---|---|---|---|---|---|---|
-| 1 | C1 | `nfc_normalize` | shared | Any unicode text | NFC-normalized text | Already-NFC text | Required by SSRM `content_hash` invariant |
+| 1 | C1 | `nfc_normalize` | shared | Any unicode text | NFC-normalized text | Already-NFC text | Required by SAGE `content_hash` invariant |
 | 2 | C2 | `strip_soft_hyphens` | shared | Text containing U+00AD (`­`) | Text without U+00AD | No soft hyphens | Soft hyphens are invisible but token-costly |
 | 3 | C3 | `normalize_ligatures` | shared | Text containing presentation-form ligatures (`fi`, `fl`, `ffi`, `ffl`, `ſt`, `st`, `ff`) and NBSP | Text with whitelist-expanded ligatures and regular spaces | None of the whitelist characters present | Whitelist-only — does not run blanket NFKC, which would fold superscripts and CJK compatibility characters |
 | 4 | C4 | `normalize_quotes_dashes` | shared | Smart quotes (`“”‘’`) and ellipsis (`…`) | Straight quotes (`""''`) and three-dot ellipsis | No smart quotes or ellipsis | En-dash and em-dash are preserved (semantic) |
@@ -305,7 +305,7 @@ class SourceMeta:
 
 ### Field-by-field
 
-| Field | Filled by | Required for SSRM contract |
+| Field | Filled by | Required for SAGE contract |
 |---|---|---|
 | `title_hint` | All converters when source metadata has a title (PDF `/Title`, DOCX `dc:title`, HTML `<title>`, otherwise `None`) | No — `frontmatter.derive_title` falls back to first H1, then filename |
 | `authors` | PDF (`/Author` parsed), DOCX (`dc:creator`), HTML (`<meta name="author">`), TXT (always `[]`). v1.0.2 adds body-text extraction and an arxiv API enrichment via `heuristics.extract_authors`. | No — empty `[]` is valid |
@@ -318,11 +318,11 @@ class SourceMeta:
 | `source_file` | All file inputs; URL inputs `None` | No — extension field |
 | `source_url` | URL inputs only; file inputs `None` | No — extension field |
 | `doc_type` | All converters | Yes — emitted as `type` in the YAML |
-| `extracted_via` | All converters | Yes — non-SSRM extension but required for traceability |
+| `extracted_via` | All converters | Yes — non-SAGE extension but required for traceability |
 | `lane` | All converters | Yes — drives pipeline routing |
 
 The four "required" fields above are required for the v1.0 contract to be
-fillable, not for SSRM strict conformance. Strict SSRM has a different
+fillable, not for SAGE strict conformance. Strict SAGE has a different
 required-fields list — see [output-format.md](output-format.md) for that
 distinction.
 

{any2md-1.0.6 → any2md-1.0.7}/docs/cli-reference.md

@@ -268,7 +268,7 @@ that defines what each key means.
 
 ### `--auto-id`
 
-Generate an SSRM-conformant `document_id` of the form
+Generate an SAGE-conformant `document_id` of the form
 `{PREFIX}-{YYYY}-{TYPE}-{SHA8}`. Defaults: `PREFIX=LOCAL`, `TYPE=DOC`. Override
 via `[document_id]` in `.any2md.toml` (`publisher_prefix`, `type_code`).
 

{any2md-1.0.6 → any2md-1.0.7}/docs/output-format.md

@@ -31,22 +31,22 @@ non-empty, single-line, and YAML-escaped. None of those guarantees come free —
 they exist because every any2md output goes through the same final emitter and
 because every field in this document has a derivation rule that's tested.
 
-## The SSRM connection
+## The SAGE connection
 
-any2md's frontmatter is **SSRM-compatible**. SSRM (Structured Security
-Reasoning Markdown) is a documented schema for LLM-consumable security
+any2md's frontmatter is **SAGE-compatible**. SAGE (Security Analysis
+and Guidance Exchange) is a documented schema for LLM-consumable security
 research documents — its primary audience is producers of threat intelligence
 and security guidance who want a stable shape for downstream RAG and LLM
-analysis. SSRM v1.0-RC1 is the version this contract tracks.
+analysis. SAGE v1.0-RC1 is the version this contract tracks.
 
 "Compatible" rather than "strict" because most documents any2md converts are
-not security research. SSRM has fields with controlled vocabularies —
+not security research. SAGE has fields with controlled vocabularies —
 `document_type`, `content_domain`, `tlp`, `frameworks_referenced` — that don't
-have plausible defaults for an arbitrary PDF or web page. Strict SSRM
+have plausible defaults for an arbitrary PDF or web page. Strict SAGE
 validators reject empty or unknown values for those fields. any2md's choice is
 to emit the fields with empty defaults (`""` or `[]`) and `status: "draft"`, so
-the output is machine-readable in the SSRM shape but doesn't claim to be a
-finished SSRM document. If you produce real SSRM-conforming security research,
+the output is machine-readable in the SAGE shape but doesn't claim to be a
+finished SAGE document. If you produce real SAGE-conforming security research,
 populate those fields explicitly via [`--meta` or `.any2md.toml`](cli-reference.md#configuration-meta-and-meta-file).
 
 The fields below are grouped: identity, classification, provenance, integrity,
@@ -134,15 +134,15 @@ records when any2md wrote it).
 
 **auto** | type: `string` (controlled vocabulary)
 
-**Derivation:** Always `"draft"` for converted documents. SSRM allows
+**Derivation:** Always `"draft"` for converted documents. SAGE allows
 non-controlled-vocab values for other fields when `status` is `"draft"`, which
 is why this is the default — it's how an any2md output declares "I have an
-SSRM-compatible shape but I have not been authored as SSRM."
+SAGE-compatible shape but I have not been authored as SAGE."
 
 **Example:** `"draft"`
 
 **Common mistake:** Overriding to `"published"` via `--meta` for documents
-that haven't actually been reviewed. SSRM consumers may treat
+that haven't actually been reviewed. SAGE consumers may treat
 `status: "published"` as a signal that the controlled-vocabulary fields are
 trustworthy. Don't claim a status the content doesn't earn.
 
@@ -150,7 +150,7 @@ trustworthy. Don't claim a status the content doesn't earn.
 
 **user** | type: `string` (controlled vocabulary or empty)
 
-**Derivation:** Empty `""` by default. SSRM defines a controlled vocabulary
+**Derivation:** Empty `""` by default. SAGE defines a controlled vocabulary
 (e.g. `"guidance"`, `"vuln_advisory"`, `"threat_report"`) but any2md cannot
 infer it from a generic document.
 
@@ -161,7 +161,7 @@ infer it from a generic document.
 
 **user** | type: `array<string>`
 
-**Derivation:** Empty `[]` by default. SSRM controlled vocabulary
+**Derivation:** Empty `[]` by default. SAGE controlled vocabulary
 (e.g. `"ai_security"`, `"cloud"`, `"identity"`).
 
 **Example empty:** `[]`
@@ -199,7 +199,7 @@ otherwise empty. User overrides commonly set this for corpus-wide attribution.
 **auto** | type: `object` (`{authored_by: string}` minimum)
 
 **Derivation:** Always emitted with `authored_by: "unknown"` because any2md
-converts content; it does not author it. SSRM's `generation_metadata` block
+converts content; it does not author it. SAGE's `generation_metadata` block
 exists to record who or what produced the document (a human, a model, a
 collaboration). If you ran any2md as part of an authoring workflow, override
 the value via `--meta generation_metadata.authored_by=human`.
@@ -218,8 +218,8 @@ generation_metadata:
 ```
 
 **Common mistake:** Adding fields under `generation_metadata` and expecting
-SSRM validators to accept them. The SSRM schema for this block has its own
-shape — consult the SSRM specification before adding non-standard subfields.
+SAGE validators to accept them. The SAGE schema for this block has its own
+shape — consult the SAGE specification before adding non-standard subfields.
 
 ### `content_hash`
 
@@ -300,7 +300,7 @@ that.
 
 **user** | type: `array<string>` and `string`
 
-**Derivation:** Empty by default. SSRM-specific fields (security frameworks
+**Derivation:** Empty by default. SAGE-specific fields (security frameworks
 the document references; traffic-light-protocol marking). User-supplied via
 `--meta` or `.any2md.toml`.
 
@@ -660,7 +660,7 @@ tampered with after generation.
 This schema describes the v1.0 frontmatter block. Conditional fields
 (`keywords`, `abstract_for_rag`, `pages`, `word_count`, `source_file`,
 `source_url`, `produced_by`) are documented here as optional; they're omitted
-from the frontmatter when not set. SSRM-only fields a user might add (`tlp`,
+from the frontmatter when not set. SAGE-only fields a user might add (`tlp`,
 `frameworks_referenced`, etc.) are listed as additional valid fields.
 
 ```json
@@ -799,7 +799,7 @@ from the frontmatter when not set. SSRM-only fields a user might add (`tlp`,
 
 The schema sets `additionalProperties: true` because users add fields via
 `--meta` and `.any2md.toml` that are not part of the v1.0 contract. A stricter
-schema for SSRM-conforming outputs would set this to `false` and add the SSRM
+schema for SAGE-conforming outputs would set this to `false` and add the SAGE
 controlled-vocabulary constraints to `document_type`, `content_domain`, and
 related fields. Use this schema as a starting point for downstream validation
 and tighten it for your environment.

{any2md-1.0.6 → any2md-1.0.7}/docs/superpowers/plans/2026-04-26-any2md-v1-phase1-foundation.md

@@ -2,7 +2,7 @@
 
 > **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking.
 
-**Goal:** Restructure any2md into the v1.0 architecture (centralized frontmatter + pipeline + SourceMeta) and rewire all 4 existing converters through it without changing extraction backends. End state: every output file carries SSRM-compatible frontmatter with deterministic `content_hash`, body is NFC-normalized + LF-ended, and a `1.0.0a1` prerelease lands on TestPyPI.
+**Goal:** Restructure any2md into the v1.0 architecture (centralized frontmatter + pipeline + SourceMeta) and rewire all 4 existing converters through it without changing extraction backends. End state: every output file carries SAGE-compatible frontmatter with deterministic `content_hash`, body is NFC-normalized + LF-ended, and a `1.0.0a1` prerelease lands on TestPyPI.
 
 **Architecture:** Two-lane post-processing pipeline (structured / text), shared cleanup stages always last, single YAML emitter (`frontmatter.py`). In Phase 1 the structured lane is empty (no Docling yet) and the text lane is empty (T1–T6 land in Phase 3); only the shared cleanup C1–C7 runs.
 
@@ -736,7 +736,7 @@ Expected: FAIL with `ModuleNotFoundError: any2md.frontmatter`.
 - [ ] **Step 3: Create `any2md/frontmatter.py` skeleton**
 
 ```python
-"""SSRM-compatible YAML frontmatter emitter.
+"""SAGE-compatible YAML frontmatter emitter.
 
 See spec §3 (frontmatter contract) and §5.0 (SourceMeta dataclass).
 This module is the single producer of the YAML block — converters
@@ -842,7 +842,7 @@ Stage = Callable[[str, "PipelineOptions"], str]
 
 
 def nfc_normalize(text: str, _options: "PipelineOptions") -> str:
-    """C1: NFC unicode normalization. Required by SSRM §5.1 for content_hash."""
+    """C1: NFC unicode normalization. Required by SAGE §5.1 for content_hash."""
     return unicodedata.normalize("NFC", text)
 
 
@@ -1502,7 +1502,7 @@ git commit -m "feat(pipeline): C7 validate (read-only, emits warnings)"
 
 ```python
 # tests/unit/test_content_hash.py
-"""Tests for content_hash determinism (SSRM §5.1)."""
+"""Tests for content_hash determinism (SAGE §5.1)."""
 
 from any2md.frontmatter import compute_content_hash
 
@@ -1557,7 +1557,7 @@ import unicodedata
 
 
 def compute_content_hash(body: str) -> str:
-    """SHA-256 of NFC-normalized, LF-line-ended body. SSRM §5.1.
+    """SHA-256 of NFC-normalized, LF-line-ended body. SAGE §5.1.
 
     The body MUST be the post-pipeline output (after C1–C5). This function
     re-applies NFC and LF normalization defensively so callers can pass any
@@ -1898,7 +1898,7 @@ git commit -m "feat(frontmatter): derive_title with H1/hint/filename fallback ch
 
 ---
 
-## Task 21: Frontmatter `compose()` — full SSRM-compatible YAML emitter
+## Task 21: Frontmatter `compose()` — full SAGE-compatible YAML emitter
 
 **Files:**
 - Modify: `any2md/frontmatter.py`
@@ -1908,7 +1908,7 @@ git commit -m "feat(frontmatter): derive_title with H1/hint/filename fallback ch
 
 ```python
 # tests/unit/test_frontmatter_compose.py
-"""Tests for frontmatter.compose() — SSRM-compatible output."""
+"""Tests for frontmatter.compose() — SAGE-compatible output."""
 
 from datetime import date
 
@@ -1945,7 +1945,7 @@ def _meta(**overrides) -> SourceMeta:
     return SourceMeta(**base)
 
 
-def test_compose_emits_required_ssrm_fields():
+def test_compose_emits_required_sage_fields():
     body = "# Title\n\nbody\n"
     out = compose(body, _meta(), PipelineOptions())
     fm, _ = _split_frontmatter(out)
@@ -2092,7 +2092,7 @@ def _emit_array(values: list[str]) -> str:
 
 
 def compose(body: str, meta: SourceMeta, options: PipelineOptions) -> str:
-    """Build a complete SSRM-compatible Markdown document.
+    """Build a complete SAGE-compatible Markdown document.
 
     Steps:
     1. Normalize body to NFC + LF endings (matches content_hash invariant).
@@ -2117,7 +2117,7 @@ def compose(body: str, meta: SourceMeta, options: PipelineOptions) -> str:
     today = _date_cls.today().isoformat()
     fm_date = meta.date or today
 
-    # 3. Emit YAML in SSRM-defined order
+    # 3. Emit YAML in SAGE-defined order
     lines: list[str] = ["---"]
     lines.append(f"title: {_emit_value(title)}")
     lines.append('document_id: ""')
@@ -2163,7 +2163,7 @@ Expected: all PASS.
 
 ```bash
 git add any2md/frontmatter.py tests/unit/test_frontmatter_compose.py
-git commit -m "feat(frontmatter): compose() SSRM-compatible YAML emitter"
+git commit -m "feat(frontmatter): compose() SAGE-compatible YAML emitter"
 ```
 
 ---
@@ -2283,7 +2283,7 @@ from any2md.cli import main
 from any2md.pipeline import PipelineOptions
 
 
-def test_txt_end_to_end_writes_ssrm_compat_output(fixture_dir, tmp_output_dir, monkeypatch):
+def test_txt_end_to_end_writes_sage_compat_output(fixture_dir, tmp_output_dir, monkeypatch):
     monkeypatch.setattr(
         "sys.argv",
         ["any2md", "-o", str(tmp_output_dir), str(fixture_dir / "ligatures_and_softhyphens.txt")],
@@ -2478,7 +2478,7 @@ def convert_txt(
     force: bool = False,
     strip_links_flag: bool = False,
 ) -> bool:
-    """Convert a plain-text file to v1.0 SSRM-compatible Markdown."""
+    """Convert a plain-text file to v1.0 SAGE-compatible Markdown."""
     if options is None:
         options = PipelineOptions(strip_links=strip_links_flag)
 
@@ -3467,7 +3467,7 @@ echo
 echo "Outputs:"
 ls -la "$OUT_DIR"
 echo
-echo "Inspect each for: SSRM frontmatter, content_hash present, body NFC + LF, no garbled chars."
+echo "Inspect each for: SAGE frontmatter, content_hash present, body NFC + LF, no garbled chars."
 ```
 
 - [ ] **Step 2: Make executable + run**
@@ -3600,12 +3600,12 @@ Replace the `## [Unreleased]` heading and contents with:
 
 This is the first prerelease of any2md v1.0. Phase 1 of 5: foundation only.
 No Docling, no new CLI flags. Output frontmatter has been rewritten to be
-SSRM-compatible — this is a breaking change for downstream consumers
+SAGE-compatible — this is a breaking change for downstream consumers
 parsing v0.7 output. See `docs/superpowers/specs/2026-04-26-any2md-v1-design.md`
 for the full v1.0 design.
 
 ### Added
-- New `any2md/frontmatter.py` module (SSRM-compatible YAML emitter, `SourceMeta`).
+- New `any2md/frontmatter.py` module (SAGE-compatible YAML emitter, `SourceMeta`).
 - New `any2md/pipeline/` package with shared cleanup stages C1–C7
   (NFC normalization, soft-hyphen strip, ligature normalization,
   quote/dash normalization, whitespace collapse, footnote-marker strip,
@@ -3615,7 +3615,7 @@ for the full v1.0 design.
 - pytest test suite covering pipeline, frontmatter, validators, and per-format integration.
 
 ### Changed
-- **BREAKING:** Output frontmatter shape is SSRM-compatible. New required fields:
+- **BREAKING:** Output frontmatter shape is SAGE-compatible. New required fields:
   `document_id` (empty), `version`, `date`, `status: "draft"`, `document_type` (empty),
   `content_domain`, `authors`, `organization`, `generation_metadata`, `content_hash`.
   `source_file`, `pages`, `word_count`, and `type` are retained as any2md
@@ -3715,7 +3715,7 @@ PYTHONPATH=/tmp/any2md_test_install python -m any2md \
 head -20 /tmp/any2md_smoke/web_page.md
 ```
 
-Expected: help text shows; web_page.md has SSRM-compat frontmatter.
+Expected: help text shows; web_page.md has SAGE-compat frontmatter.
 
 - [ ] **Step 8: Final commit (none needed — everything already committed)**
 
@@ -3763,7 +3763,7 @@ Approximate critical path: A → C → D/E → F → G → H → I = 12 sequenti
 ## Self-review summary
 
 Spec coverage:
-- §3 Frontmatter contract → Tasks 8, 16–22 (full SSRM-compat shape, content_hash, all derivation helpers).
+- §3 Frontmatter contract → Tasks 8, 16–22 (full SAGE-compat shape, content_hash, all derivation helpers).
 - §4 Pipeline (C1–C7) → Tasks 9–15. Text/structured lanes registered empty in Task 7 (Phase 2/3 fill them).
 - §5 Per-format converters → Tasks 23–26 (TXT, HTML, DOCX, PDF). Phase 1 PDF is pymupdf4llm only.
 - §6 CLI → Task 27 preserves v0.7 flags routing through new pipeline. New flags are Phase 4.