File Classification Framework: Sage Library Vault

Naming Convention

Delimiters

Casing

Hard Limits

Segment Grammar

PER Domain — Personal Forge Notes

PER.{Pillar}.{Topic_FunctionalCategory_Subject}.{Type}.{Descriptor}.{Variable?} — 5–6 segments

CS.AK Domain — Akatsuki Forge Notes

CS.AK.{Mission}.{Type}.{Descriptor}.{Variable?} — 5–6 segments

CS.YB Domain — Yūrei Butai Forge Notes

With end client and sub-brand (parent-group end-client + sub-brand-specific work):

CS.YB.{Client}.{EndClient}.{SubBrand}.{Mission}.{Type}.{Descriptor}.{Variable?} — 8–9 segments

The {SubBrand} slot is occupied if and only if {EndClient} represents a parent organisation that holds multiple commercial sub-brands AND the deliverable targets a specific sub-brand. Group-level work omits the slot. See the FCF SubBrand Slot Revision Proposal for the full slot-occupancy rule, frontmatter convention, and worked examples.

With end client (no sub-brand):

CS.YB.{Client}.{EndClient}.{Mission}.{Type}.{Descriptor}.{Variable?} — 7–8 segments

Without end client: Positions 4+ shift up. CS.YB.{Client}.{Mission}.{Type}.{Descriptor}.{Variable?} — 6–7 segments

Standard Collections

Input subtype patterns:

One contributor per filename. Additional contributors in YAML only. Title truncated at last complete PascalCase word within 30 chars — no ellipsis.

Folder Taxonomy

Folder Naming Convention

Folder names are deliberately differentiated from file names to prevent visual and semantic ambiguity between the two namespaces.

Character-level rules:

Separator semantics:

Single-word folder names use neither separator: personal, lisa, csdao, bjj, artefacts.

Scope: The convention applies uniformly across all folder levels. The hierarchy encodes structural depth — individual folder names do not need to re-encode it.

Folder Tree

vault-root/
├── personal/
│   ├── self_actualisation/
│   │   ├── mind/
│   │   ├── body/
│   │   └── spirit/
│   ├── love/
│   │   ├── kazoku-ai/
│   │   ├── renai/
│   │   ├── yujo/
│   │   ├── jiko-ai/
│   │   └── jihi/
│   ├── expertise/
│   │   ├── ninjutsu/
│   │   ├── genjutsu/
│   │   └── sagyojutsu/
│   └── foundations/
├── cipher_shinobi/
│   ├── akatsuki/
│   │   ├── csdao/
│   │   ├── the_system/
│   │   ├── safety_net/
│   │   ├── model_maker/
│   │   └── lisa/
│   └── yurei-butai/
│       ├── ClientA/
│       ├── client-b/
│       └── client-c/
├── entities/
├── prompts/
│   └── copilot_commands/
├── templates/
│   ├── executable/
│   └── structural/
├── inputs/
│   ├── articles/
│   ├── books/
│   ├── papers/
│   ├── podcasts/
│   ├── tweets/
│   └── videos/
├── temporal/
│   ├── daily/
│   ├── weekly/
│   ├── monthly/
│   └── yearly/
├── definitions/
├── ideas/
├── calculations/
├── bjj/
├── artefacts/
│   ├── builds/
│   │   └── {project-name}/
│   ├── code/
│   │   └── {project-name}/
│   ├── configs/
│   │   └── {project-name}/
│   ├── data/
│   │   └── {project-name}/
│   ├── media/
│   │   ├── bjj-assets/          
│   │   ├── icons/               
│   │   ├── pixel_art/           
│   │   ├── shinobi_icons/       
│   │   └── {project-name}/
│   ├── pdfs/
│   │   └── {project-name}/
│   └── scripts/
│       └── {project-name}/
├── bases/
├── fleeting/
├── cache/
└── Home.md

Nesting rules: Forge PER folders mirror hierarchy to topic level. CS.AK mission folders optional. CS.YB client folders mandatory; end-client subfolders optional. Standard notes filed into collection folder.

Artefact Governance

Placement Rules

All non-markdown files produced within the vault workflow — regardless of which mission, project, or subject they serve — must be stored within artefacts/{type}/{project-subfolder}/ paths. Non-markdown files must never be placed in mission folders, subject folders, or any other vault directory that primarily contains markdown notes.

Placement matrix:

Project subfolder convention: The project subfolder name is the mission's lowercase-hyphenated name (e.g., ClientA/, ClientA/, growth-energy/, east-coast-hydrogen/). The same name must be used consistently across all artefacts/{type}/ directories for the same mission. General or unscoped artefacts use general/. Subfolders are created on first use — never pre-created empty.

Disambiguation:

ArtefactMap — Data Subtype

An ArtefactMap is a Data-type Forge note that lives inside a mission or subject folder and serves as a navigable manifest linking that folder's markdown context to non-markdown artefacts stored in the artefacts/ directory hierarchy.

Naming grammar: {Namespace}.Data.ArtefactMap

Where {Namespace} is the FCF namespace segment chain for the parent folder:

Required frontmatter fields: ArtefactMap notes use standard Forge YAML for their parent domain. The following fields are required on every instance:

Additionally, include all domain-specific fields required by the parent domain's segment grammar (PER: pillar, topic, subject; CS.AK: division, mission; CS.YB: division, client, end_client, mission as applicable).

Body metadata: ArtefactMap notes include a Last Updated field in the note body (not in YAML frontmatter) that must be updated to the current ISO 8601 timestamp on every modification:

**Last Updated**: 2026-03-12T19:30:00Z

Template: TMPL.ArtefactMap

ArtefactMap Entry Format

Each entry within an ArtefactMap section follows this structure:

### filename.ext

- **Path**: `artefacts/{type}/{project-subfolder}/filename.ext`
- **Link**: !`filename.ext` (embeddable) or `filename.ext` (non-embeddable)
- **Description**: [Brief description of the artefact's purpose and context]
- **Date Added**: YYYY-MM-DD

Link format rules:

ArtefactMap Maintenance Protocol

On artefact creation:

1. Place the artefact in the correct artefacts/{type}/{project-subfolder}/ path per the placement matrix
2. Check whether an ArtefactMap exists in the parent mission/subject folder
3. If no ArtefactMap exists, create one from TMPL.ArtefactMap
4. If an ArtefactMap exists, read it and append a new entry under the appropriate type section
5. Update the Last Updated body field to the current ISO 8601 timestamp

On artefact deletion or move:

1. Update the corresponding ArtefactMap entry (new path) or remove it (deletion)
2. Update Last Updated
3. If all entries are removed, delete the ArtefactMap note

Artefact Folder Taxonomy

artefacts/  
├── builds/ ← Compiled or bundled distribution outputs  
│ └── {project-name}/ ← Created per-project as needed  
├── code/ ← Source code archives and application bundles  
│ └── {project-name}/  
├── configs/ ← Generated configuration file outputs  
│ └── {project-name}/  
├── data/ ← JSON, CSV, XML, TSV data exports  
│ └── {project-name}/  
├── media/ ← Images and visual assets  
│ ├── bjj-assets/ (legacy — retained)  
│ ├── icons/ (legacy — retained)  
│ ├── pixel_art/ (legacy — retained)  
│ ├── shinobi_icons/ (legacy — retained)  
│ └── {project-name}/ ← Created per-project as needed  
├── pdfs/ ← PDF documents  
│ └── {project-name}/  
└── scripts/ ← Standalone shell and automation scripts  
└── {project-name}/

Edge Case Rules

Classification System

Primary Classification: Forge vs. Standard

Forge Note Types

Standard Note Types

Filename Construction Decision Tree

START
│
Q1: Tactical asset for a specific mission?
├─ YES → Q2
└─ NO → Q8
│
Q2: Which domain?
├─ Personal (PER) → Q3
└─ Cipher Shinobi (CS) → Q5
│
Q3: Which Pillar? (Consult Activity Classification Matrix)
├─ SA / LV / EX / FDN
│
Q3a: Determine Topic_FunctionalCategory_Subject compound
│  Topic + optional FunctionalCategory + Subject codes from Matrix
│  → {TOPIC}_{FunctionalCategory}_{SUBJECT} or {TOPIC}_{SUBJECT} or {TOPIC}
│  FunctionalCategory uses Title case; Topic and Subject use ALLCAPS
│  → Q4
│
Q4: Forge note type?
├─ Docu │ Matter │ Intel │ Data │ Code │ TechSpec
├─ MissionBrief │ Seed │ Log │ Meeting
│
→ BUILD: PER.{Pillar}.{Topic_FunctionalCategory_Subject}.{Type}.{Descriptor}.{Variable?}
│
Q5: CS division? (Consult Mission Matrix)
├─ Akatsuki (AK) → Q6
└─ Yūrei Butai (YB) → Q7
│
Q6: AK mission → Type (per Q4)
→ BUILD: CS.AK.{Mission}.{Type}.{Descriptor}.{Variable?}
│
Q7: YB engagement → Type (per Q4)
├─ End client exists, parent group with sub-brands, work targets a specific sub-brand:
│  → BUILD: CS.YB.{Client}.{EndClient}.{SubBrand}.{Mission}.{Type}.{Descriptor}.{Variable?}
│  (Mission elidable when work spans sub-brand's full scope per FCF SubBrand Slot rule)
├─ End client exists, no sub-brand layer (or group-level work):
│  → BUILD: CS.YB.{Client}.{EndClient}.{Mission}.{Type}.{Descriptor}.{Variable?}
└─ No end client:
   → BUILD: CS.YB.{Client}.{Mission}.{Type}.{Descriptor}.{Variable?}
│
Q8: Standard collection type?
├─ Person/org profile → ENT.{Name}
├─ AI instruction (doc) → PRMT.{Client}.{Subtype}.{Descriptor}
├─ AI instruction (exec) → CMD.{Subtype}.{Descriptor}
├─ Note scaffold → TMPL.{Descriptor}
├─ External source → Q9
├─ Time-bounded record → TEMP.{DateId}
├─ Term definition → DEF.{Term}
├─ Math method → CALC.{Method}
├─ Internal ideation → IDEA.{Subtype}.{Descriptor}
├─ BJJ technique → BJJ.{Subtype}.{Technique}.{Variant?}
└─ No match → flag framework limitation
│
Q9: Input subtype?
├─ Article / Book / Tweet → IN.{Subtype}.{Author}.{Title}
├─ Paper → IN.Paper.{Author}.{Title}.{Year}
├─ Video → IN.Video.{Creator}.{Channel}.{Title}
└─ Podcast → IN.Podcast.{Host}.{Show}.{EpTitle}

Classification Matrix Consultation Protocol

1. Extract key terms from note content: entities, activities, mission identifiers.
2. Select matrix:
   • PER domain → PER.EX.SAG_SYSX.Data.ActivityClassMatrix.Tobi
   • CS domain → CS.AK.CSDAO.Data.MissionMatrix
3. Locate matching row and extract canonical values:
   • PER: pillar, topic, subject
   • CS.YB: client, end_client, sub_brand (when EndClient is a parent group), mission — use Mission Shorthand (from the Mission Matrix) for the filename segment; use the full mission name for the YAML mission field; the sub_brand: YAML field mirrors the filename {SubBrand} slot when present
   • CS.AK: mission
4. Apply to YAML using expanded values (e.g., "Sagyōjutsu", not "SAG"; "Coaching Platform", not "Coaching"). Consult the Abbreviated Code Reference below for filename ↔ YAML translation, including the YB Mission Shorthand Codes table.
5. Matrix gap? Classify by best judgement. Flag in YAML: note: Pending [Matrix Name] formalisation - [gap description].

Abbreviated Code Reference

Domains & Divisions:

Pillars:

Topics:

Representative Subject Codes (canonical source: PER.EX.SAG_SYSX.Data.ActivityClassMatrix.Tobi):

YB Mission Shorthand Codes (canonical source: CS.AK.CSDAO.Data.MissionMatrix):

Collection Codes (Standard):