dkzver/Sanctification
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Moved some files around and made cleanup better

Browse Source
This commit is contained in:
Daniel
2026-09-14 19:01:08 -07:00
parent 50b234104a
commit 97ed7f05c8
866 changed files with 404 additions and 1612 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
docs/card-workspace.md
View File

@@ -28,7 +28,9 @@ in-progress/cards/BE-002-the-fall/
high/textless/
```
Every resolution has the same four printing directories. Normal and Borderless include applicable glyph masks; Textless and Boundless need no glyph protection, though an explicit zero map may be retained. Source/build records describe the whole revision and belong outside resolution folders. Resolution manifests contain exact dimensions and hashes for their own exports.
Every local assembly has the same four printing directories. Normal and Borderless include applicable glyph masks; Textless and Boundless need no glyph protection, though an explicit zero map may be retained. Source/build records describe the whole revision and belong outside resolution folders. Resolution manifests contain exact dimensions and hashes for their own exports.
Git retention is intentionally smaller while a revision is under `in-progress/`: source inputs, text records, review material and each resolution manifest are retained, but generated `med/` and `high/` files and low-resolution masks/editable masters are ignored. The four `low/[printing]/card.png` files are the tracked printing references. A local build still writes and validates all resolutions. When approved, the complete local package moves outside the scoped ignore rules into `artifacts/cards/`, where every production export is retained.
Use the exact master-catalogue ID for `cardId` (for example **BE-002**). Keep the catalogue display title in `title` and a readable **ID-title** directory name in `folderName` (for example **BE-002-the-fall**). Build/application references select by `cardId` and revision through the progress index; they do not reconstruct the directory from the title. Folder names are generated when a card is first scaffolded and stay stable across later title edits unless an explicit rename updates the profile/index. Number new revisions explicitly (`v01`, `v02`, …); do not infer selection or approval from file timestamps. A card's root `card.json` selects its revision. [The progress index](../in-progress/index.json) resolves selected revisions in either location.
@@ -50,7 +52,9 @@ artifacts/cards/BE-002-the-fall/
high/ # 2000 × 2800, same printing directories
```
The accepted directory holds one current approved card. Its manifest retains the revision number; there is no revision folder under `artifacts/cards/`. Working revisions retain their `revisions/v01/` structure. When a newer revision is approved, the previous accepted package moves to `in-progress/cards/[ID-title]/history/accepted-[revision]/` before the new package takes its place. Linked inputs remain pinned to the version they used.
The accepted directory holds one current approved card. Its manifest retains the revision number; there is no revision folder under `artifacts/cards/`. When a newer revision is approved, the replacement remains self-contained and the previous acceptance becomes a compact record at `in-progress/cards/[ID-title]/history/accepted-[revision]/`. Superseded working revisions similarly move to `history/revisions/[revision]/`.
Compact history keeps the original full manifest as `full-manifest.json`, content/build and textual source/review records, and one 500 × 700 `card.png` for each available printing. Art-only iterations keep one 500 × 700 art reference. Medium/high exports, masks, source rasters and extra review images are deleted after acceptance. A `record.json` explains the disposition; compact records are historical references, not buildable canonical revisions.
## New work
@@ -82,7 +86,13 @@ python3 tools/card-production/card_workspace.py approve \
--card BE-002 --revision v02 --approval-note 'Exact user approval wording'
```
The tool validates the assembled revision, moves the entire revision to `artifacts/cards/BE-002-the-fall/`, records the approval, updates the index and compatibility links, and adjusts linked SVG/input paths for the new directory depth. It does not install harness fixtures. Approved revisions are frozen; revisions to them begin in a new working revision. Previous accepted packages remain in working history when replaced; the helper preserves their linked inputs and updates the current selection.
The tool validates the assembled revision, internalizes any live input borrowed from older work, moves the entire revision to `artifacts/cards/BE-002-the-fall/`, records the approval, updates the index and compatibility links, and adjusts linked SVG/input paths for the new directory depth. It then compacts superseded working and accepted revisions using the retention rule above. It does not install harness fixtures. Approved revisions are frozen; revisions to them begin in a new working revision.
To apply the same cleanup once to a card accepted before this policy:
```sh
python3 tools/card-production/card_workspace.py compact --card BE-002
```
## Existing work migration