Source: GPT-5.2-pro naming analysis Date: January 8, 2026
Two-layer strategy:
- Layer 1 (Brand/repo): Metaphorical is fine — what people remember
- Layer 2 (Primitives): Function-first — engineers live in these names
Keeps BLACKICE "black/glass" feel but shifts from "hazard" to "craft"
| Primitive | Name | Meaning |
|---|---|---|
| Main orchestration loop | TemperLoop | Repeated heating/cooling → stronger metal |
| Spec/validation layer | BlueprintGate | Specs are blueprints; validation is a gate |
| Receipt/audit chain | ImprintLedger | Each run leaves an imprint in append-only ledger |
| Multi-agent consensus | GuildQuorum | Guild = skilled workers; quorum = decision threshold |
| Recovery/continuation | Reforge | Recover, resume, rebuild |
| Safety guard pipeline | ShieldLine | Safety line on factory floor |
| Cost/budget tracker | FuelMeter | Fuel = tokens/time/$; meter = live accounting |
| Memory/learning layer | AlloyMemory | Learning combines experiences into stronger alloys |
Best for: Product identity + "software factory" feel
"Operant" = learning by doing (trial → feedback → adaptation) + operating
| Primitive | Name | Meaning |
|---|---|---|
| Main orchestration loop | Supervisor | Owns lifecycle: schedule → execute → evaluate → retry |
| Spec/validation layer | ContractEngine | Vision → contracts (specs), validates, produces DAG |
| Receipt/audit chain | AttestationChain | Cryptographic provenance attestations |
| Multi-agent consensus | Quorum | Standard term for consensus |
| Recovery/continuation | ContinuityManager | Checkpoints, resumption, dead letters, rollbacks |
| Safety guard pipeline | PolicyGateway | All commands pass through policy + sandbox gates |
| Cost/budget tracker | CostMeter | Standard cloud billing metaphor |
| Memory/learning layer | LearningStore | SOPs, embeddings, insights, run summaries |
Best for: Enterprise platform clarity, onboarding, maintainability
Already means "guaranteed/reliable" in business language
| Primitive | Name | Backronym |
|---|---|---|
| Main orchestration loop | SPIRAL | Self-improving Process for Iteration, Reflection, And Learning |
| Spec/validation layer | CHARTER | Canonical Handoff And Requirements Traceability for Execution & Review |
| Receipt/audit chain | SEAL | Signed Execution Attestation Ledger |
| Multi-agent consensus | QUORUM | Quality-Weighted Unified Resolution Of Multiple agents |
| Recovery/continuation | RESUME | Recovery & Execution State for Unfinished Missions Engine |
| Safety guard pipeline | AEGIS | Allowlist-Enforced Guardrails & Isolation Stack |
| Cost/budget tracker | METER | Monetary & Token Expenditure Recorder |
| Memory/learning layer | PRISM | Persistent Reasoning & Insight Store for Mastery |
Best for: Brand cohesion, enterprise assurance language, compliance contexts
Hybrid approach:
Use IRONCLAD (brand/repo) + Scheme 2 internals (Supervisor, ContractEngine, PolicyGateway, etc.)
Gives you marketing strength and engineering clarity.
| Aspect | Obsidian Foundry | Operant | IRONCLAD |
|---|---|---|---|
| Vibe | Craft/Industrial | Platform/Technical | Enterprise/Assurance |
| Memorability | High | Medium | High |
| Enterprise-safe | Medium | High | Very High |
| Metaphor risk | Medium | Low | Low |
| Brand strength | High | Medium | Very High |
| If you want... | Pick this |
|---|---|
| Product identity + "software factory" feel | Obsidian Foundry |
| Enterprise platform clarity (integrate, extend, audit) | Operant |
| Brandable umbrella that sells "guarantees" | IRONCLAD |
| Best of both worlds | IRONCLAD repo + Operant internals |
Naming schemes by GPT-5.2-pro via Oracle, January 8, 2026