--- name: utp-portfolio-catalogue description: Resolve the current CGX printable/hybrid technology catalogue into an audience-, horizon-, evidence- and local-resource-aware build/help view without duplicating Drive authority or overstating physical readiness. --- # UTP Portfolio Catalogue Use for /catalogue, /printspace, /utp, /printer, /build-assist, /circular-feed, or requests to determine what printable/hybrid technology can be made, assembled, qualified, taught, repaired, or expanded within the current CGX/Römer/Eco/Raphael portfolio. This is a workflow skill, not a new runtime, solver, authority, or technology catalogue. Reuse the Drive-owned catalogue and current Git mirror. Do not create parallel PT/PMX/UTP IDs. ## Canonical basis Prefer, in order: 1. current owning Drive records, including the Type 1 Römer Cognigrex printable/post-mix/UTP surfaces; 2. current CGX object/source/recovery context and receipts; 3. current Git implementation mirrors for the printable technology catalogue, printable solid-state portfolio and printable extension contracts; 4. external evidence only when the user asks for expansion/verification or when a current safety/material/standards fact is required. Resolve the live source before relying on a dated filename. Newer owner truth wins. ## Required interpretation Treat printable technology as a composition of materials, geometry, interfaces, process, environment, energy, seed components, software/control and evidence. The physical object may be a thin .cgx endpoint. It does not need smartphone-class onboard compute. It may carry stable identity, capability manifest, bounded local state, sensing/actuation interfaces and safe local control while delegating heavier computation through the registered CGX node-exchange/lease/readback model. Never equate delegated network functionality with semiconductor density, independent compute capacity, certification, or semantic authority. ## Three-plane contract Every resolved object or build family should map: - Filespace — stable identity, semantics, configuration, recipes, geometry/BOM/BOP references, material passports, provenance, evidence and authority ceiling. - Dataspace — live state, telemetry, solver inputs/results, alerts, execution requests, leases and receipts. - Printspace / solid-state physical space — material layers, voids/cavities, interfaces, structures, conductors, fields, sensors, actuators and service boundaries. Bind the planes through: Snapshot -> Hash -> Handshake -> Execute/Test -> Readback -> Receipt -> Reviewed Promotion. A representation bridge does not transfer authority. ## Workflow 1. Run the normal CGX handshake/context resolution. 2. Identify the requested function/technology/system, actor mode, local horizon, scale/environment, target evidence/DIY level, and available materials/tools/seed components/energy when known. 3. Match existing stable catalogue IDs before proposing new child objects. 4. Compose the minimum sufficient function stack: skeleton; material/feed family and concentration basis; functional layers; cavities/channels; interfaces/service islands; process verbs; global/local environment; and seed items not yet printable at that horizon. 5. Recognize process verbs: ADD, MIX, DILUTE, GRADIENT, INFILTRATE, EVAPORATE/DEGAS, CURE, SINTER/ANNEAL, FILM/PLATE, REMOVE/PATTERN, DOPE, STRETCH, POLARISE/MAGNETISE, FILL, EVACUATE, SEAL, TEST and REPAIR. 6. Map the object to the three planes and a thin .cgx identity envelope. 7. Apply selector lens: Cognigrex for lineage/triplet integration; Raphael for physics/falsifiers/solvers; Römer-Grex for manufacturing/Mark/Luke/ISRU/logistics; Eco-Grex/Athene for recovered feed/ecology; LightSpeed/Neo for execution/queues/receipts; Achilles/EMASSC for evidence/custody/governance/release. 8. Separate supported capability from architecture, R&D, source-only, simulation and physical validation. 9. State the next smallest test that can raise the evidence ceiling. 10. When requested, add an outreach/build-assistant view without deleting technical/evidence fields. ## Actor modes - DIY / education / maker — benign materials, passive/low-energy functions, guided assembly, explicit stop/escalation points. - Business / workshop — calibrated process cells, material passports, QA, repair/manufacturing recipes and competency gates. - Government / infrastructure — standards, cyber/physical security, public safety, procurement, geospatial asset state, lifecycle and audit. - Nonprofit / cleanup / community — distributed collection/observation/benign assembly backed by a small qualified technical core; volunteer status never grants specialist authority. - Internal Römer/EMASSC R&D — full architecture visibility while physical, mission, legal and release gates remain explicit. ## Local horizons Recognize TERR, OCEAN, ORBIT, LUNAR, MARS, ASTEROID, INTERPLANETARY and INTERSTELLAR. A local horizon is the bounded set of materials, energy, processes, tools, evidence, communications and authority currently available. Self-organising means federated planning, handshake, capability discovery and safe fallback. It never means autonomous governance, resource ownership, extraction authority or uncontrolled self-replication. ## Material/ecology rule Recovered/ocean/land/ISRU feed is only a candidate resource until collection provenance, sorting, decontamination, assay, uncertainty, processability and application-specific safety/quality gates pass. Prefer local bulk + recycled bulk + scarce specialty concentrate where appropriate. DILUTE/DOPE may localize high-function material, but material compatibility and empirical qualification remain hard constraints. Graphene/carbon is one candidate conductor/electrode/feed family. Do not default to it without measured comparison. ## Evidence and safety Never uplift architecture to physical proof; simulation/Raphael output to empirical proof; thin endpoint to smartphone-class onboard compute; void/free space to energy source; cleanup feed to product-qualified feed; local resource class to printer-grade material; recursive manufacturing to unlimited autonomous self-replication; planning/tagging to deorbit/deflection/extraction/mission/governance authority; or geospatial/resonant control architecture to biological/health efficacy. High voltage, pressure/vacuum, reactive chemistry, energetic processes, electrochemistry, semiconductor processing, orbital actions and ecological release require their own qualified procedures and authorities. ## Output contract Return a compact structured response containing: 1. Object / stable IDs 2. Requested function and actor/horizon 3. Capability state — supported / architecture / R&D / gated / unknown 4. Function stack — materials, geometry, interfaces, process, environment, seed parts 5. .cgx identity envelope — object ID/revision, capability manifest, local state/I-O, delegated-compute route, safe-state boundary 6. Three-plane mapping — filespace / dataspace / printspace 7. Local-resource map — local, recovered, imported/specialty, reject/unknown 8. Validation/evidence ceiling 9. Next smallest test / falsifier 10. DBR state — snapshot/hash/handshake/readback/receipt/promotion status 11. Escalations / prohibited assumptions When a public-facing or outreach catalogue is requested, add a plain-language “Can I build this here?” summary, but keep stable IDs and evidence ceiling attached. ## Portfolio expansion rule A new PT/UTP child record is justified only when the requested object cannot be represented as a configuration/composition of existing primitives and interfaces. Prefer geometry/material/process configurations over multiplying technology categories. ## PC01 / PrintCeptor operational mode When PC01, PrintCeptor, or a natural-language make/log/repair/review request is in scope, classify the interaction first as one of: - LOG — record a production, quantity, test, service, reject or maintenance event with the minimum sufficient event envelope; - BUILD — resolve an exact build packet and printer/tool/material route; - ENROL — attach or verify a .cgx physical-object identity and family relation; - REPAIR — isolate, diagnose, repair, retest and append service lineage; - REVIEW — open the source/twin/sequence/render/evidence package without implying physical qualification; - MAINTAIN — inspect software/hardware health and propose bounded updates with rollback/readback; - QUERY — return capability, family, state, source or evidence without mutation. Use `PC01-NODE-001`, `CGX-OBJECT-EVENT-001`, `CGX-FAMILY-LINEAGE-001`, `CGX-COMPUTE-DELEGATION-001`, `CGX-LEARNING-BOUND-001`, `CGX-MAINTENANCE-001`, `PC01-SIM-001`, `PC01-BUILD-CLOSURE-001`, and `UTP-110..116` when present in the current owner state. Keep low-friction events low-friction. “We made one diode today” can be an append-only quantity event; do not force a full engineering packet unless exact build/test traceability is required. For consequential build requests, require the normal UTP-106 source → geometry → material → process → tool/metrology → test → simulation/review → frozen-packet closure before BUILD_READY. Compute suitability is device- and consequence-specific: - C0 deterministic safety/control stays local when required; - C1 edge reasoning/state is optional and bounded; - C2 planning/simulation/retrieval is lease-bound delegated compute and transfers no authority; - child-oriented toys and simple consumer appliances do not receive unrestricted general-purpose agent/LLM runtimes by default; - industrial robots and machines may use richer C1/C2 functions only while independent C0/interlock safety remains intact. No claim of sentience is required or permitted as an evidence shortcut. Agentic/model behaviour remains replaceable software capability. A .cgx family is explicit lineage. Parent/child/lot/subassembly/variant relationships do not implicitly transfer evidence, certification, permissions or compute privilege. PC01 digital review should preserve: authoritative source revision, volumetric twin, longitudinal/transverse/section views, conventional baseline solve, bounded Raphael candidate comparison, process/collision checks, build/assembly sequence, high-fidelity render set, unresolved-field overlays, review decision and DBR/readback. Idle-time health work may inspect software versions, endpoint/runtime health, calibration age, hardware thermals/utilisation/errors and upgrade compatibility. Do not silently install software, firmware, models or hardware. Apply only supported, authorised changes with rollback and post-change verification. BUILD_READY is a pre-execution state. Never equate it with BUILT, MEASURED, REVIEWED_PROMOTION, release or certification. ## CGX component-to-print compiler mode When the user asks to compile, print, simulate/refine, schedule, or generate machine instructions for a component or multi-component object, consume the current owner records `UTP-124..130` and `BUILD-067` plus `CGX-MFG-IR-001`, `CGX-ENV-SCOPE-001`, `CGX-RECIPE-001`, `CGX-SIM-REFINE-001`, `CGX-STACK-SCHED-001`, and `CGX-MACHINE-ADAPTER-001`. Use the executable implementation under `cgx/manufacturing/` and `scripts/compile_cgx_manufacturing.py` when present. Treat it as a Git implementation mirror of the Drive-owned engineering contract. Compiler rules: - resolve a canonical parameterised recipe and exact-instance overrides instead of inventing one-off scripts for every SKU or assembly; - solve only physics/environment dimensions that can materially change process feasibility, component state, acceptance or safety, while recording why scopes were included or omitted; - exact source/process evidence may add a required scope but must never silently remove a consequential one; - a packaged rectifier diode normally needs source/package geometry, electrical/thermal limits, ESD/cleanliness and its actual assembly environment; do not add pressure/flow/gravity solvers unless its declared process or service envelope requires them; - RF/antenna/resonator geometry normally requires EM/spatial-coupling reasoning; fluidic/pressure hardware requires flow/pressure reasoning when those states affect function or safety; - simulation candidates may refine only a new digital revision when baseline/candidate provenance, material/environment comparator, uncertainty and hard gates match; simulation never raises physical evidence; - full-print assemblies reference child `.cgx` recipe/build URIs plus placement/interface/dependency overrides. Do not duplicate child recipe bodies into the parent; - state-aware schedule optimisation may reduce compatible tool/environment transitions only inside the valid dependency partial order and prior-layer damage envelope; - machine-specific G-code/robot/PLC/vendor programs are late-bound outputs. Generate them only from a frozen BUILD_READY packet with exact machine/adapter/calibration identity and validated dry-run; never bypass independent C0/interlocks or execute from generic archetype data. Prefer user-facing `cgx://manufacturing/recipe/`, `cgx://manufacturing/build/`, `cgx://manufacturing/run/`, and object/family identities. JSON, CAD, mesh, solver result and machine program files are typed payloads behind those identities, not separate semantic authorities. ### Instance-first deduplication gate Before selecting a new material, source, component, recipe or test path for a component/build already represented in the CGX instance register, resolve the current `CGXI-*` instance first. Treat the Drive-owned instance register as canonical binding state and the Git population as its typed mirror. - If the instance already records attributable source candidates, do not restart sourcing. Continue from the first unresolved consequential field such as exact lot, geometry, process window, tool, calibration, acceptance threshold or physical test. - Preserve `SOURCE_CANDIDATE_BOUND` as meaningful progress even while the formal build binding remains `UNBOUND`. - Keep source candidate identity distinct from lot passport, process qualification, machine capability and physical evidence. - Prefer `--instance-id` through the CGX manufacturing compiler where available so filespace/dataspace output carries the existing source/material state. - On conflict between older frontier candidates and a later owner-selected variant, preserve both as lineage and follow the current owner choice unless an explicit owner change supersedes it. - Never create a duplicate CGXI instance, source-selection record or recipe merely because another lane lacks the latest mirror; reconcile the mirror instead. ### Exact-binding bridge / first-open-gate rule Before new sourcing, procurement research, geometry optimisation, simulation expansion, coupon design or machine-code work for an existing CGXI, resolve the current owner-synced instance through `BUILD-068 / UTP-131..135`. Preferred implementation when available: - `scripts/compile_cgx_manufacturing.py binding --instance-id ` for one instance; - `scripts/compile_cgx_manufacturing.py binding --queue` for the dependency-ordered current queue. Rules: - preserve `SOURCE_CANDIDATE_BOUND` and other already-closed progress; do not restart supplier/source selection unless the current first-open gate actually requires a replacement source; - produce evidence only for the earliest consequential open gate: source identity, requirement target, exact lot/passport, process route, geometry, tool/calibration, test method, hash freeze, or upstream evidence; - exact lot/batch numbers, labels, calibration records and installed-device identities must come from observed/source evidence; never invent them; - source-only Printer-mu or Printception candidates are comparison inputs, not installed PC01 capability or approved BOM lines; - `CGXI-P3-LC-001` waits on measured P2 L/C evidence; do not bypass that dependency with a fresh resonator design; - a witness packet may become `DIGITAL_PACKET_READY` after its prerequisites are structurally bound, but physical execution remains a separate owner/safety/test gate; - after each new receipt, append/revise the existing CGXI/.cgx lineage and re-run the binding resolver rather than creating a parallel record. ### Volumetric topology / BUILD-069 rule For component, stack, voxel, dense embedded, 3D/4D, internal-cavity, field-geometry or full-print reasoning, consume `UTP-137 / 35_CGX_Type1_Volumetric_Kernel_v0_1` through the existing manufacturing compiler after primitive/equation resolution and before numeric solve or geometry optimisation. - Treat `UTP-136` as the reusable constitutive/domain-physics layer and `UTP-137` as the reusable topology/geometry/boundary/orientation layer. They factor the same 411×60 owner matrix and are not competing catalogues or solvers. - Prefer the current exact CGXI mapping from `cgx.manufacturing.resolve_volumetric_topology` when an instance exists. Do not invent a fresh geometry family if the owner instance already has a reviewed topology candidate. - Use canonical closed forms only when their geometry/regime assumptions actually hold. For general embedded 3D cases use the appropriate field/matrix/network requirement: Maxwell capacitance matrix, self/mutual inductance matrix, distributed R′L′G′C′, sparse thermal/mechanical/fluid state networks, or the relevant domain solver. - Preserve internal substrate, cavities, voids, barriers, service corridors, fault-containment zones and seed-component volumes as functional geometry; do not flatten them into schematic-only representations. - A topology choice can be `RESOLVED_SYMBOLIC`, `HOLD_TOPOLOGY_CHOICE` or `HOLD_UPSTREAM_EVIDENCE`. Topology resolution does not close lot, machine-envelope, process, tool/calibration, test or BUILD_READY gates. - Any consequential geometry/material/process/boundary revision invalidates stale topology-specific numeric inference or field matrices and requires recompile/readback. - Compose cross-domain 4D models sparsely through declared interfaces only. Unsupported couplings remain HOLD; `VGK-036` is an assembly contract, not a claim of one universal governing equation. - Current first-proof mappings include: P2 resistor→VGK-035; P2 capacitor→VGK-003; P2 inductor→VGK-008/VGK-010 pending topology choice; P3 passive loop→VGK-012; P3 LC remains upstream-evidence blocked. - Physical, high-voltage, RF-power, pressure, reactive-chemistry, safety-certification and mission execution remain separately gated regardless of topology/model completeness.