ARMOR Minimal Stable

This repository is the implementation and maintenance layer for ARMOR's shared memory architecture. It stores the router, tests, documentation, migration tooling, and read-only knowledge-quality tooling. It does not store live ARMOR business memory.

Identity

Repository:
licat233/armor-memory

Shared Skill:
/Users/licat/AI-Agent-Skills/armor-memory

Active Vault:
/Users/licat/armor-vault

Frozen Legacy Vault:
/Users/licat/Obsidian-V7.2-Legacy

The architecture name is ARMOR Minimal Stable.

Do not call this system V8.0.

Current Status

• Status: Production / Stable
• Migration: Completed on 2026-07-28
• Active Vault: /Users/licat/armor-vault
• Legacy V7.2: Frozen and read-only
• Last verified full-suite baseline before the knowledge-quality upgrade: 104 passed
• Knowledge-quality focused validation on 2026-09-05: 12 passed

Architecture Flow

Codex / Claude Code / Hermes Agent
                ↓
Shared Skill: armor-memory
                ↓
Router / explicit knowledge-quality tools
                ↓
ARMOR_VAULT_ROOT
                ↓
/Users/licat/armor-vault

• The Shared Skill defines memory behavior and routing discipline.
• The Router determines the destination path.
• Knowledge-quality checks are explicit, read-only diagnostics.
• ARMOR_VAULT_ROOT resolves the active Vault location.
• The Vault stores ARMOR business memory.
• This repository stores architecture, code, tests, and maintenance tools.
• The frozen V7.2 Vault is historical and read-only.

Active Vault Structure

armor-vault/
├── 00-System/
├── 01-Knowledge/
├── 02-Projects/
├── 03-Records/
├── 04-Research/
├── 90-Inbox/
└── 99-Archive/

• 00-System/: system rules, start points, and operational guidance
• 01-Knowledge/: canonical business knowledge and reusable facts
• 02-Projects/: active projects and persistent workspaces
• 03-Records/: published records, meetings, journals, and communications
• 04-Research/: notes and source collections for ongoing investigation
• 90-Inbox/: explicitly unresolved material only
• 99-Archive/: inactive Minimal Stable material retained for reference

Core Principles

• Minimal structure over lifecycle complexity.
• Object type determines location.
• Draft and Proposal are statuses, not permanent root directories.
• Projects and canonical Knowledge remain separate.
• Skill controls behavior; Vault stores business memory.
• The Vault remains the sole durable knowledge source of truth.
• Derived tools must not become a second authoritative store.
• Business memory must not contain unrelated personal machine administration.
• Bulk changes must be backed up, manifest-driven, and reversible.
• Do not recreate V7.2 lifecycle architecture.
• Do not call the system V8.0.

Routing

Shared entry points:

Skill:
/Users/licat/AI-Agent-Skills/armor-memory/SKILL.md

Router wrapper:
/Users/licat/AI-Agent-Skills/armor-memory/scripts/route.sh

The Router should be used before a persistent write when the destination is not already explicit.

Journal destinations resolve under:

/Users/licat/armor-vault/03-Records/Journal/<year>/

The Router determines the destination path only. It does not silently create business content.

Knowledge Quality

ARMOR Minimal Stable includes a deliberately small read-only knowledge-quality layer.

Agent entry point:

bash /Users/licat/AI-Agent-Skills/armor-memory/scripts/knowledge.sh check

Repository entry point:

python3 minimal-stable/scripts/armor-knowledge.py check

The check command scans only 01-Knowledge/ and reports authority, provenance, and possible duplicate-title issues. It does not edit, merge, delete, promote, or demote knowledge.

For a material canonical change, a current file and candidate file can be compared with:

python3 minimal-stable/scripts/armor-knowledge.py diff current.md candidate.md

The diff is diagnostic only. Human approval remains the authority gate.

Knowledge-quality maintenance is explicit-only. Ordinary reads and writes remain lightweight and do not trigger hidden full-Vault scans.

Update Policy

ARMOR Minimal Stable does not perform automatic update discovery.

Updates are explicitly initiated by the human operator. Agents do not check repository versions, Skill versions, CHANGELOG files, or update status during normal memory tasks.

Update process:

1. The operator requests an update.
2. The Agent reads the specific update instructions.
3. Relevant files are backed up.
4. Approved changes are applied.
5. Tests and Agent verification are run.
6. The operator reviews the result.

Normal Agent sessions must not perform version checks. Normal memory operations must not read update metadata. No automatic update notification is required. No background update process is used. No Agent may silently self-update.

VERSION and CHANGELOG.md may exist as human-facing release records, but ordinary memory work must not depend on them.

Development And Testing

Run tests from the repository root:

cd /Volumes/MacData/projects/AI-Agent-Memory-Architecture
python3 -m pytest minimal-stable/tests -v

The last previously verified full-suite baseline is 104 passed.

For the knowledge-quality upgrade, the focused new suite was validated separately:

python3 -m pytest minimal-stable/tests/test_armor_knowledge.py -q

Result on 2026-09-05: 12 passed.

Do not replace the full-suite baseline with an inferred total until the complete repository suite has actually been run in the real repository checkout.

Run the full test suite after changes to routing, Vault path handling, Skill integration, migration tooling, or knowledge-quality behavior.

Backup And Rollback

Final V7.2 archive:

/Users/licat/ARMOR-Migration-Backups/armor-v7.2-final-20260728-212459.tar.gz

SHA-256:

b646b7c56575f86d583bb7e1c1fddf412bce3b269be70945b0575502b87f90b6

Rollback guide:

/Users/licat/ARMOR-Migration-Reports/final-acceptance-20260728-172412/ROLLBACK-V7.2-FREEZE.md

Rollback must never overwrite /Users/licat/armor-vault.

Legacy Status

/Users/licat/Obsidian-V7.2-Legacy remains frozen, read-only, and available only for historical verification or disaster recovery.

It must not be used as the active ARMOR business-memory source.

Operational Rules

Do

• Write new ARMOR memory only to /Users/licat/armor-vault.
• Use the shared Skill and Router.
• Keep Knowledge stable and reusable.
• Store active work in Projects.
• Store historical evidence in Records.
• Run knowledge-quality checks only when explicitly requested.
• Run tests after architectural changes.
• Back up files before bulk changes.

Do Not

• Do not write to /Users/licat/Obsidian-V7.2-Legacy.
• Do not restore V7.2 Hooks, Skill, or Router behavior.
• Do not recreate 90-Drafts, 93-Proposals, or other V7.2 lifecycle roots.
• Do not add automatic update checks to normal Agent workflows.
• Do not silently overwrite existing Vault files.
• Do not treat diagnostic warnings as permission to modify canonical knowledge.
• Do not mix personal machine maintenance into ARMOR business memory.
• Do not rename the shared Skill away from armor-memory.

Repository Layout

minimal-stable/
minimal-stable/00-System/
minimal-stable/scripts/
minimal-stable/tests/
shared/
shared/frontmatter/
shared/document-map/

minimal-stable/scripts/ Router, migration utilities, and the read-only knowledge-quality tool.

minimal-stable/tests/ Automated verification for routing, migration safety, Agent integration, and knowledge-quality behavior.

shared/ Shared standards and templates retained by the architecture repository. Historical V7.2-oriented standards must not override active Minimal Stable rules.

Migration History

• 513 effective business files were migrated.
• The old Vault was backed up and frozen.
• Active V7.2 instructions and active path dependencies were reduced to zero.
• Codex, Claude Code, and Hermes Agent all passed post-freeze verification.
• Detailed reports are stored under /Users/licat/ARMOR-Migration-Reports/.

Final Authority Statement

/Users/licat/armor-vault is the sole active ARMOR business-memory Vault.

This README.md is the authoritative repository-level status document for ARMOR Minimal Stable.