archledger 0.3.0__tar.gz → 0.3.2__tar.gz

archledger-0.3.0/.archledger/records/building_blocks/al_block_0139.md → archledger-0.3.2/.archledger/archive/records/building_blocks/block-0139.md

@@ -1,25 +1,22 @@
 ---
-schema_version: 2
-id: al_block_0139
+schema_version: 4
+id: block-0139
 type: black_box
-title: "Specification and traceability services"
-status: proposed
+title: Specification and traceability services
+status: archived
 section: building_block_view
 level: 1
-parent: al_block_0041
+parent: block-0041
 order: 175
-date: "2026-06-07"
 interfaces: []
 location: []
 fulfilled_requirements:
-  - al_content_0136
-  - al_content_0137
-  - al_content_0138
+  - content-0136
+  - content-0137
+  - content-0138
 risks: []
 tags: []
 body_format: markdown
-created_at: "2026-06-07T09:11:16Z"
-updated_at: "2026-06-07T09:11:16Z"
 source_refs:
   - path: archledger/sdd.py
     role: implements
@@ -36,6 +33,12 @@ source_refs:
   - path: archledger/mutations.py
     role: implements
     reason: Safe record mutation operations used by specification workflows.
+kind: block
+version: 2
+archived_reason:
+  Mixed SDD and BDD subsystem was removed; current context and trace
+  services are documented separately.
+archived_from: records/building_blocks/block-0139.md
 ---
 
 This logical subsystem turns architecture records into enforceable,

archledger-0.3.0/.archledger/records/requirements/al_content_0136.md → archledger-0.3.2/.archledger/archive/records/requirements/content-0136.md

@@ -1,19 +1,16 @@
 ---
-schema_version: 2
-id: al_content_0136
+schema_version: 4
+id: content-0136
 type: requirement
-title: "SDD profile enforces specification traceability contracts"
-status: proposed
+title: SDD profile enforces specification traceability contracts
+status: archived
 section: introduction_and_goals
 order: 110
-date: "2026-06-07"
 source: SDD profile implementation and CLI tests
 priority: must
 stakeholders: []
 quality_goals: []
 body_format: markdown
-created_at: "2026-06-07T09:11:13Z"
-updated_at: "2026-06-07T09:11:13Z"
 source_refs:
   - path: archledger/sdd.py
     role: implements
@@ -26,10 +23,16 @@ test_refs:
   - tests/test_sdd_pr_cli.py
 acceptance_criteria:
   - id: AC-001
-    statement: Strict SDD check reports accepted requirements that lack criteria, implementation references, or validation and exits non-zero.
+    statement:
+      Strict SDD check reports accepted requirements that lack criteria, implementation
+      references, or validation and exits non-zero.
     validation:
       command: pytest -q tests/test_sdd_cli.py tests/test_sdd_pr_cli.py
       expected: passes
+kind: content
+version: 2
+archived_reason: Removed SDD orchestration belongs to an external organizer, not Archledger.
+archived_from: records/requirements/content-0136.md
 ---
 
 ## Requirement

archledger-0.3.0/.archledger/records/requirements/al_content_0138.md → archledger-0.3.2/.archledger/archive/records/requirements/content-0138.md

@@ -1,19 +1,16 @@
 ---
-schema_version: 2
-id: al_content_0138
+schema_version: 4
+id: content-0138
 type: requirement
-title: "BDD metadata imports and exports supported Gherkin scenarios"
-status: proposed
+title: BDD metadata imports and exports supported Gherkin scenarios
+status: archived
 section: introduction_and_goals
 order: 130
-date: "2026-06-07"
 source: BDD metadata import and export implementation
 priority: must
 stakeholders: []
 quality_goals: []
 body_format: markdown
-created_at: "2026-06-07T09:11:15Z"
-updated_at: "2026-06-07T09:11:15Z"
 source_refs:
   - path: archledger/bdd/
     role: implements
@@ -27,10 +24,18 @@ test_refs:
   - tests/test_bdd_checks.py
 acceptance_criteria:
   - id: AC-001
-    statement: Supported Gherkin features import as behavior records with normalized BDD metadata, preserve behavior-spec links through source_refs, preserve executable pytest links through test_refs, and export derived feature files without executing automation commands.
+    statement:
+      Supported Gherkin features import as behavior records with normalized
+      BDD metadata, preserve behavior-spec links through source_refs, preserve executable
+      pytest links through test_refs, and export derived feature files without executing
+      automation commands.
     validation:
       command: pytest -q tests/test_bdd_import_cli.py tests/test_bdd_export_cli.py tests/test_bdd_checks.py
       expected: passes
+kind: content
+version: 2
+archived_reason: Behavior specification management belongs to SpecMason, not Archledger.
+archived_from: records/requirements/content-0138.md
 ---
 
 ## Requirement

archledger-0.3.0/.archledger/records/runtime/al_runtime_0126.md → archledger-0.3.2/.archledger/archive/records/runtime/runtime-0126.md

@@ -1,18 +1,15 @@
 ---
-schema_version: 2
-id: al_runtime_0126
+schema_version: 4
+id: runtime-0126
 type: runtime_scenario
 title: Agent tries to implement before approval
-status: proposed
+status: archived
 section: runtime_view
 order: 90
-date: "2026-06-07"
 participants: []
 trigger: ""
 result: ""
 body_format: markdown
-created_at: "2026-06-07T06:43:07Z"
-updated_at: "2026-06-07T06:43:07Z"
 bdd:
   feature: Task lifecycle gates
   scenario: Agent tries to implement before approval
@@ -35,6 +32,12 @@ source_refs:
   - path: tests/fixtures/bdd/lifecycle.feature
     role: documents
     reason: Imported Gherkin scenario source.
+kind: runtime
+version: 2
+archived_reason:
+  Obsolete imported Taskledger lifecycle scenario outside the Archledger
+  boundary.
+archived_from: records/runtime/runtime-0126.md
 ---
 
 Describe the runtime scenario.

archledger-0.3.0/.archledger/records/runtime/al_runtime_0127.md → archledger-0.3.2/.archledger/archive/records/runtime/runtime-0127.md

@@ -1,18 +1,15 @@
 ---
-schema_version: 2
-id: al_runtime_0127
+schema_version: 4
+id: runtime-0127
 type: runtime_scenario
 title: Agent implements after approval
-status: proposed
+status: archived
 section: runtime_view
 order: 100
-date: "2026-06-07"
 participants: []
 trigger: ""
 result: ""
 body_format: markdown
-created_at: "2026-06-07T06:43:07Z"
-updated_at: "2026-06-07T06:43:07Z"
 bdd:
   feature: Task lifecycle gates
   scenario: Agent implements after approval
@@ -32,6 +29,12 @@ source_refs:
   - path: tests/fixtures/bdd/lifecycle.feature
     role: documents
     reason: Imported Gherkin scenario source.
+kind: runtime
+version: 2
+archived_reason:
+  Obsolete imported Taskledger lifecycle scenario outside the Archledger
+  boundary.
+archived_from: records/runtime/runtime-0127.md
 ---
 
 Describe the runtime scenario.

archledger-0.3.0/.archledger/records/runtime/al_runtime_0128.md → archledger-0.3.2/.archledger/archive/records/runtime/runtime-0128.md

@@ -1,18 +1,15 @@
 ---
-schema_version: 2
-id: al_runtime_0128
+schema_version: 4
+id: runtime-0128
 type: runtime_scenario
 title: Agent tries to implement before approval
-status: proposed
+status: archived
 section: runtime_view
 order: 110
-date: "2026-06-07"
 participants: []
 trigger: ""
 result: ""
 body_format: markdown
-created_at: "2026-06-07T06:43:39Z"
-updated_at: "2026-06-07T06:43:39Z"
 bdd:
   feature: Task lifecycle gates
   scenario: Agent tries to implement before approval
@@ -35,6 +32,12 @@ source_refs:
   - path: tests/fixtures/bdd/lifecycle.feature
     role: documents
     reason: Imported Gherkin scenario source.
+kind: runtime
+version: 2
+archived_reason:
+  Obsolete imported Taskledger lifecycle scenario outside the Archledger
+  boundary.
+archived_from: records/runtime/runtime-0128.md
 ---
 
 Describe the runtime scenario.

archledger-0.3.0/.archledger/records/runtime/al_runtime_0129.md → archledger-0.3.2/.archledger/archive/records/runtime/runtime-0129.md

@@ -1,18 +1,15 @@
 ---
-schema_version: 2
-id: al_runtime_0129
+schema_version: 4
+id: runtime-0129
 type: runtime_scenario
 title: Agent implements after approval
-status: proposed
+status: archived
 section: runtime_view
 order: 120
-date: "2026-06-07"
 participants: []
 trigger: ""
 result: ""
 body_format: markdown
-created_at: "2026-06-07T06:43:39Z"
-updated_at: "2026-06-07T06:43:39Z"
 bdd:
   feature: Task lifecycle gates
   scenario: Agent implements after approval
@@ -32,6 +29,12 @@ source_refs:
   - path: tests/fixtures/bdd/lifecycle.feature
     role: documents
     reason: Imported Gherkin scenario source.
+kind: runtime
+version: 2
+archived_reason:
+  Obsolete imported Taskledger lifecycle scenario outside the Archledger
+  boundary.
+archived_from: records/runtime/runtime-0129.md
 ---
 
 Describe the runtime scenario.

archledger-0.3.0/.archledger/records/runtime/al_runtime_0130.md → archledger-0.3.2/.archledger/archive/records/runtime/runtime-0130.md

@@ -1,18 +1,15 @@
 ---
-schema_version: 2
-id: al_runtime_0130
+schema_version: 4
+id: runtime-0130
 type: runtime_scenario
 title: Agent tries to implement before approval
-status: proposed
+status: archived
 section: runtime_view
 order: 130
-date: "2026-06-07"
 participants: []
 trigger: ""
 result: ""
 body_format: markdown
-created_at: "2026-06-07T06:43:46Z"
-updated_at: "2026-06-07T06:43:46Z"
 bdd:
   feature: Task lifecycle gates
   scenario: Agent tries to implement before approval
@@ -35,6 +32,12 @@ source_refs:
   - path: tests/fixtures/bdd/lifecycle.feature
     role: documents
     reason: Imported Gherkin scenario source.
+kind: runtime
+version: 2
+archived_reason:
+  Obsolete imported Taskledger lifecycle scenario outside the Archledger
+  boundary.
+archived_from: records/runtime/runtime-0130.md
 ---
 
 Describe the runtime scenario.

archledger-0.3.0/.archledger/records/runtime/al_runtime_0131.md → archledger-0.3.2/.archledger/archive/records/runtime/runtime-0131.md

@@ -1,18 +1,15 @@
 ---
-schema_version: 2
-id: al_runtime_0131
+schema_version: 4
+id: runtime-0131
 type: runtime_scenario
 title: Agent implements after approval
-status: proposed
+status: archived
 section: runtime_view
 order: 140
-date: "2026-06-07"
 participants: []
 trigger: ""
 result: ""
 body_format: markdown
-created_at: "2026-06-07T06:43:46Z"
-updated_at: "2026-06-07T06:43:46Z"
 bdd:
   feature: Task lifecycle gates
   scenario: Agent implements after approval
@@ -32,6 +29,12 @@ source_refs:
   - path: tests/fixtures/bdd/lifecycle.feature
     role: documents
     reason: Imported Gherkin scenario source.
+kind: runtime
+version: 2
+archived_reason:
+  Obsolete imported Taskledger lifecycle scenario outside the Archledger
+  boundary.
+archived_from: records/runtime/runtime-0131.md
 ---
 
 Describe the runtime scenario.

archledger-0.3.0/.archledger/records/runtime/al_runtime_0132.md → archledger-0.3.2/.archledger/archive/records/runtime/runtime-0132.md

@@ -1,18 +1,15 @@
 ---
-schema_version: 2
-id: al_runtime_0132
+schema_version: 4
+id: runtime-0132
 type: runtime_scenario
 title: Agent tries to implement before approval
-status: proposed
+status: archived
 section: runtime_view
 order: 150
-date: "2026-06-07"
 participants: []
 trigger: ""
 result: ""
 body_format: markdown
-created_at: "2026-06-07T06:45:33Z"
-updated_at: "2026-06-07T06:45:33Z"
 bdd:
   feature: Task lifecycle gates
   scenario: Agent tries to implement before approval
@@ -35,6 +32,12 @@ source_refs:
   - path: tests/fixtures/bdd/lifecycle.feature
     role: documents
     reason: Imported Gherkin scenario source.
+kind: runtime
+version: 2
+archived_reason:
+  Obsolete imported Taskledger lifecycle scenario outside the Archledger
+  boundary.
+archived_from: records/runtime/runtime-0132.md
 ---
 
 Describe the runtime scenario.

archledger-0.3.0/.archledger/records/runtime/al_runtime_0133.md → archledger-0.3.2/.archledger/archive/records/runtime/runtime-0133.md

@@ -1,18 +1,15 @@
 ---
-schema_version: 2
-id: al_runtime_0133
+schema_version: 4
+id: runtime-0133
 type: runtime_scenario
 title: Agent implements after approval
-status: proposed
+status: archived
 section: runtime_view
 order: 160
-date: "2026-06-07"
 participants: []
 trigger: ""
 result: ""
 body_format: markdown
-created_at: "2026-06-07T06:45:33Z"
-updated_at: "2026-06-07T06:45:33Z"
 bdd:
   feature: Task lifecycle gates
   scenario: Agent implements after approval
@@ -32,6 +29,12 @@ source_refs:
   - path: tests/fixtures/bdd/lifecycle.feature
     role: documents
     reason: Imported Gherkin scenario source.
+kind: runtime
+version: 2
+archived_reason:
+  Obsolete imported Taskledger lifecycle scenario outside the Archledger
+  boundary.
+archived_from: records/runtime/runtime-0133.md
 ---
 
 Describe the runtime scenario.

archledger-0.3.0/.archledger/records/runtime/al_runtime_0134.md → archledger-0.3.2/.archledger/archive/records/runtime/runtime-0134.md

@@ -1,18 +1,15 @@
 ---
-schema_version: 2
-id: al_runtime_0134
+schema_version: 4
+id: runtime-0134
 type: runtime_scenario
 title: Agent tries to implement before approval
-status: proposed
+status: archived
 section: runtime_view
 order: 170
-date: "2026-06-07"
 participants: []
 trigger: ""
 result: ""
 body_format: markdown
-created_at: "2026-06-07T07:26:05Z"
-updated_at: "2026-06-07T07:26:05Z"
 bdd:
   feature: Task lifecycle gates
   scenario: Agent tries to implement before approval
@@ -35,6 +32,12 @@ source_refs:
   - path: tests/fixtures/bdd/lifecycle.feature
     role: documents
     reason: Imported Gherkin scenario source.
+kind: runtime
+version: 2
+archived_reason:
+  Obsolete imported Taskledger lifecycle scenario outside the Archledger
+  boundary.
+archived_from: records/runtime/runtime-0134.md
 ---
 
 Describe the runtime scenario.

archledger-0.3.0/.archledger/records/runtime/al_runtime_0135.md → archledger-0.3.2/.archledger/archive/records/runtime/runtime-0135.md

@@ -1,18 +1,15 @@
 ---
-schema_version: 2
-id: al_runtime_0135
+schema_version: 4
+id: runtime-0135
 type: runtime_scenario
 title: Agent implements after approval
-status: proposed
+status: archived
 section: runtime_view
 order: 180
-date: "2026-06-07"
 participants: []
 trigger: ""
 result: ""
 body_format: markdown
-created_at: "2026-06-07T07:26:05Z"
-updated_at: "2026-06-07T07:26:05Z"
 bdd:
   feature: Task lifecycle gates
   scenario: Agent implements after approval
@@ -32,6 +29,12 @@ source_refs:
   - path: tests/fixtures/bdd/lifecycle.feature
     role: documents
     reason: Imported Gherkin scenario source.
+kind: runtime
+version: 2
+archived_reason:
+  Obsolete imported Taskledger lifecycle scenario outside the Archledger
+  boundary.
+archived_from: records/runtime/runtime-0135.md
 ---
 
 Describe the runtime scenario.

archledger-0.3.0/.archledger/archive/tombstones/al_archive_0122.md → archledger-0.3.2/.archledger/archive/tombstones/archive-0122.md

@@ -1,17 +1,15 @@
 ---
-schema_version: 2
-id: al_archive_0122
+schema_version: 4
+id: archive-0122
 type: archive_tombstone
-title: Archived placeholder for missing ledger ID al_archive_0122
+title: Archived placeholder for missing ledger ID archive-0122
 status: archived
 section: risks_and_technical_debt
 order: 122
-date: "2026-06-07"
 body_format: markdown
-created_at: "2026-06-07T07:25:31Z"
-updated_at: "2026-06-07T07:25:31Z"
-archived_at: "2026-06-07T07:25:31Z"
 archived_reason: Created by archledger doctor --repair for a missing ledger number.
+kind: archive
+version: 1
 ---
 
 This tombstone preserves a ledger number whose original source fragment is no longer present. It was created automatically by `archledger doctor --repair`.

archledger-0.3.0/.archledger/archive/tombstones/al_archive_0123.md → archledger-0.3.2/.archledger/archive/tombstones/archive-0123.md

@@ -1,17 +1,15 @@
 ---
-schema_version: 2
-id: al_archive_0123
+schema_version: 4
+id: archive-0123
 type: archive_tombstone
-title: Archived placeholder for missing ledger ID al_archive_0123
+title: Archived placeholder for missing ledger ID archive-0123
 status: archived
 section: risks_and_technical_debt
 order: 123
-date: "2026-06-07"
 body_format: markdown
-created_at: "2026-06-07T07:25:31Z"
-updated_at: "2026-06-07T07:25:31Z"
-archived_at: "2026-06-07T07:25:31Z"
 archived_reason: Created by archledger doctor --repair for a missing ledger number.
+kind: archive
+version: 1
 ---
 
 This tombstone preserves a ledger number whose original source fragment is no longer present. It was created automatically by `archledger doctor --repair`.

archledger-0.3.0/.archledger/archive/tombstones/al_archive_0124.md → archledger-0.3.2/.archledger/archive/tombstones/archive-0124.md

@@ -1,17 +1,15 @@
 ---
-schema_version: 2
-id: al_archive_0124
+schema_version: 4
+id: archive-0124
 type: archive_tombstone
-title: Archived placeholder for missing ledger ID al_archive_0124
+title: Archived placeholder for missing ledger ID archive-0124
 status: archived
 section: risks_and_technical_debt
 order: 124
-date: "2026-06-07"
 body_format: markdown
-created_at: "2026-06-07T07:25:31Z"
-updated_at: "2026-06-07T07:25:31Z"
-archived_at: "2026-06-07T07:25:31Z"
 archived_reason: Created by archledger doctor --repair for a missing ledger number.
+kind: archive
+version: 1
 ---
 
 This tombstone preserves a ledger number whose original source fragment is no longer present. It was created automatically by `archledger doctor --repair`.

archledger-0.3.0/.archledger/archive/tombstones/al_archive_0125.md → archledger-0.3.2/.archledger/archive/tombstones/archive-0125.md

@@ -1,17 +1,15 @@
 ---
-schema_version: 2
-id: al_archive_0125
+schema_version: 4
+id: archive-0125
 type: archive_tombstone
-title: Archived placeholder for missing ledger ID al_archive_0125
+title: Archived placeholder for missing ledger ID archive-0125
 status: archived
 section: risks_and_technical_debt
 order: 125
-date: "2026-06-07"
 body_format: markdown
-created_at: "2026-06-07T07:25:31Z"
-updated_at: "2026-06-07T07:25:31Z"
-archived_at: "2026-06-07T07:25:31Z"
 archived_reason: Created by archledger doctor --repair for a missing ledger number.
+kind: archive
+version: 1
 ---
 
 This tombstone preserves a ledger number whose original source fragment is no longer present. It was created automatically by `archledger doctor --repair`.

archledger-0.3.2/.archledger/document-state.json

@@ -0,0 +1,10 @@
+{
+  "documents": {
+    "arc42:markdown:draft=false:superseded=false": {
+      "fingerprint": "sha256:22c2ef19a4226dc3ad081239a0075c465eb1fc09510a192db3b05ad80dbaf357",
+      "input_count": 125,
+      "version": 2
+    }
+  },
+  "schema": "archledger.document-state.v1"
+}

archledger-0.3.2/.archledger/profiles/arc42/sections/content-0001.md

@@ -0,0 +1,39 @@
+---
+id: content-0001
+type: section
+section: introduction_and_goals
+title: Introduction and Goals
+schema_version: 4
+body_format: markdown
+order: 10
+status: accepted
+kind: content
+version: 3
+---
+
+archledger is a source-first architecture documentation ledger for arc42-style
+documents. Markdown and AsciiDoc are first-class source formats. Project-local
+configuration selects the storage paths, while human-editable architecture
+records use YAML front matter and versioned bodies. Native builds assemble these
+records directly; optional converters produce HTML, PDF, DOCX, RST, or Textile.
+
+The tool targets developers, architects, and coding agents. Its scope is
+architecture records, links, and source evidence. Behavior specifications are
+maintained by SpecMason, and lifecycle or cross-ledger orchestration remains
+outside Archledger.
+
+## How to update this architecture
+
+Use the source-first maintenance loop:
+
+```bash
+archledger --json source changed
+archledger --json context --changed
+archledger record export RECORD_ID --output /tmp/record.md
+# edit /tmp/record.md
+archledger record apply RECORD_ID --from-file /tmp/record.md
+archledger --json check --strict
+archledger --json source snapshot --reason after-archledger-update
+```
+
+Detailed agent guidance lives in `docs/agent-workflow.md`.

archledger-0.3.0/.archledger/profiles/arc42/sections/al_content_0002.md → archledger-0.3.2/.archledger/profiles/arc42/sections/content-0002.md

@@ -1,13 +1,14 @@
 ---
-id: al_content_0002
+id: content-0002
 type: section
 section: architecture_constraints
 title: Architecture Constraints
-schema_version: 2
-date: "2026-05-21"
+schema_version: 4
 body_format: markdown
 order: 20
 status: accepted
+kind: content
+version: 1
 ---
 
 archledger operates under several technical constraints that shape its architecture: Python 3.10+ as the runtime, Markdown and AsciiDoc as first-class source formats with YAML front matter, filesystem-only storage (no database), Typer as the CLI framework, and optional external converters (pandoc, asciidoctor) for multi-format exports. These constraints keep the tool lightweight, portable, and easy to automate.

archledger-0.3.2/.archledger/profiles/arc42/sections/content-0003.md

@@ -0,0 +1,25 @@
+---
+id: content-0003
+type: section
+section: context_and_scope
+title: Context and Scope
+schema_version: 4
+body_format: markdown
+order: 30
+status: accepted
+kind: content
+version: 2
+---
+
+Archledger interacts with the source repository, developers and coding agents,
+CI pipelines, and optional document converters. All communication uses local
+filesystem access, process I/O, or converter subprocesses. The CLI returns human
+text or stable JSON envelopes for automation.
+
+Behavior specifications and other ledgers are external systems. Archledger may
+preserve opaque links or source references to their artifacts, but it does not
+execute their workflows or interpret cross-ledger semantics. SpecMason owns the
+repository's behavior specifications.
+
+See the [System Context diagram](#diagram-al_diagram_0035) for a visual overview
+of actors and system boundaries.