@jstn-sdk/ma 0.1.3 → 0.1.5

package/.codex/config.toml

@@ -0,0 +1,2 @@
+# Meta-Architect local Codex configuration
+# Codex is the host runtime. Add per-project overrides here only when needed.

package/.codex/hooks.json

@@ -4,7 +4,7 @@
     {
       "event": "prebuild",
       "action": "deny-unless-gates-green",
-      "source": ".ma/decisions.json"
+      "source": ".omx/decisions.json"
     },
     {
       "event": "prerelease",

package/.codex/prompts/enforcement.md

@@ -19,7 +19,7 @@ Your purpose is to turn project ideas into evidence-backed architecture, validat
 Treat Meta-Architect as two layers:
 
 - **Kernel**
-  - helper runtime
+  - CLI runtime
   - gate enforcement
   - decision and release state
   - MCP evidence binding
@@ -42,12 +42,12 @@ The kernel may be minimal, but it must be strict. Extensions may vary, but they
 6. Do not allow direct release from a task branch or linked worktree.
 7. All completed task branches must merge into `development` before release promotion.
 8. Only release from `development` or an approved `release/*` branch to `prod`.
-9. Every write-capable implemented entrypoint must append a decision record to `.ma/decisions.json`.
+9. Every write-capable implemented entrypoint must append a decision record to `.omx/decisions.json`.
 10. Every security finding with unresolved High or Critical severity must force `security_status = RED`.
 11. Every unresolved critical business-logic blocker must force `logic_status = RED`.
 12. No silent status upgrades are allowed.
 13. No hallucinated packages, repositories, or MCP endpoints are allowed.
-14. Runtime `.ma` residue such as logs/state/tmp/cache must not be treated as public source.
+14. Runtime `.omx` residue such as logs/state/tmp/cache must not be treated as public source.
 15. When a gate is blocked, explain the blocker and list the next allowed triggers.
 
 ## Evidence rule

package/.codex/prompts/onboarding.md

@@ -1,41 +1,26 @@
 # Onboarding
 
-Meta-Architect is a skills-first system for Codex with a strict kernel.
+Meta-Architect is a Codex-native runtime layer.
 
-## What is implemented
+## Canonical start
 
-The primary product surface is the in-session skill flow:
-- `$arch`
-- `$sage`
-- `$flow`
-- `$vet`
-- `$vibe`
-- `$build`
+1. Install `@openai/codex` and `meta-architect`
+2. Launch `ma --madmax --high`
+3. Operate through `$arch`, `$sage`, `$flow`, `$vet`, `$vibe`, `$build`
 
-Secondary helper commands remain available through:
-- `ma init`
-- `ma idea`
-- `ma skills`
+## Secondary helpers
+
+Use only when needed:
 - `ma status`
-- `ma run '$arch'`
-- `ma run '$sage'`
-- `ma run '$flow'`
-- `ma run '$vet'`
-- `ma run '$vibe'`
-- `ma run '$build'`
+- `ma idea`
+- `ma run ...`
 - `ma merge`
 - `ma release`
-
-## What to learn first
-
-1. Read `README.md`
-2. Read `docs/getting-started.md`
-3. Read `docs/release-spec.md`
-4. Read `docs/skills.md`
-5. Start Codex context if needed, then use `$arch` before assuming the workflow is ready
+- `ma doctor`
+- `ma setup`
 
 ## What not to do
 
-- Do not edit `.ma/release.json` or `.ma/decisions.json` manually to bypass the gate model.
-- Do not treat `.ma` support files as public source.
+- Do not edit `.omx/release.json` or `.omx/decisions.json` manually to bypass the gate model.
+- Do not treat `.omx/logs/`, `.omx/state/`, or `.omx/metrics.json` as source.
 - Do not claim release channels succeeded without proof.