CTG ROM Layout v0.1.2

日本語

This document defines the canonical CTG-ROM layout for the v0.1.2 package series. The Monolith CTG-ROM content is promoted from the rc5 validation line to the v0.1.2 canon without changing its semantic rules, council duties, gate rules, or reject policy taxonomy.

Version Alignment

The v0.1.2 update changes only package-facing metadata:

• Version: 0.1.2 in governance Markdown files
• version: "0.1.2" in locale YAML files
• canonVersion: "0.1.2" in locale YAML files
• schemaVersion: "0.1.2" in locale YAML files

The canonical wording, rule text, council boundaries, gate functions, and reject reason semantics remain unchanged.

Directory Layout

rom/\n  governance/\n    ctg.monolith.canon.md\n    ctg.monolith.canon.ja.md\n    council.logos.monolith.md\n    council.logos.monolith.ja.md\n    council.ethos.monolith.md\n    council.ethos.monolith.ja.md\n    council.pathos.monolith.md\n    council.pathos.monolith.ja.md\n    gate.decision.monolith.md\n    gate.decision.monolith.ja.md\n    gate.trajectory.monolith.md\n    gate.trajectory.monolith.ja.md\n    reject.policy.monolith.md\n    reject.policy.monolith.ja.md\n  locales/\n    en-US/\n      ctg.monolith.minimal.en.yaml\n    ja-JP/\n      ctg.monolith.minimal.ja.yaml

Layering Rule

The Monolith CTG-ROM is the base layer. Developers personalize CTG-ROM by adding diff layers over this base. Do not edit the base canon to create a personalized ROM.

Personalized layers must preserve:

• Canon / Council / Gate / RejectPolicy separation
• Logos / Ethos / Pathos council boundaries
• vote-only Decision Gate input
• fail-closed handling for unknown values
• deterministic replay and traceability

Python Sample Packaging

The aikernel-net Python package includes the same CTG-ROM tree under aikernel_net.samples.ctg_rom for examples and validation. Package users can discover it through:

• ctg_rom_sample_path()
• ctg_rom_sample_files()

The Python sample is a packaged carrier of the canonical files. It must stay in sync with AIKernel.NET/rom.

Change Control

Changes to ROM semantics require a new canon review. Metadata-only version alignment for package publication is allowed when the content has already been validated and the maintainer explicitly promotes it to the release canon.