CTO / CfOC working group
The package's illustrative unitized curtain-wall panel is traced from product declarations through current CIS mating behavior, a proposed classification layer, connector selection, scoped geometry checks, and auditable receipts.
File and software boundary
A capability or rule stated in the vendored CTO v0.2.0 or CIS v0.1.3 drafts.
A structure to test with the working group. It is not part of the current file type.
Simulated data used to make the proposal inspectable. Replace it with reviewed source data.
A placement, governance, or scope question the working group still needs to resolve.
Each product identifies itself, exposes reusable geometry and properties, and declares the CIS interface addressed by a product face.
The shared interface defines two sides, ports, positions, tolerances, connection signatures, and version compatibility.
The assembly supplies the facts that change from one placement to another. Reusable products do not carry the demand of every possible building.
Software resolves a proposed interface-family classification, filters connector families, applies hard gates, then scores eligible catalog options.
A receipt records what was checked, which inputs and rules were used, the finding, and what remained outside scope.
End-to-end trace
The first two steps use current specification concepts. The remaining steps make the working proposal concrete without quietly rewriting CTO or CIS.
Identify the panel system, floor edge, placement, access, and facts needed for this question.
context.connection_condition
Resolve the same CIS and compatible versions. Confirm opposite sides, aligned ports, tolerances, and compatible signatures.
cis.id + sides + ports + signatures
Reference the proposed material-neutral interface wrapper so independent catalogs can describe solutions for the same connection intent.
project_context.interface_family_ref
Use panel type, framing condition, substrate, edge condition, and role to narrow generic connector families.
selection.eligible_families[]
Exclude options that fail required geometry, material applicability, evidence presence, or installation access.
evaluation.hard_gates[]
Rank only eligible options. Scores explain preferences and never override a failed or unknown hard gate.
selection.candidates[].score
Return the chosen connector ID, exact placement offset, two footprints, access status, protected-zone status, and evidence references.
evaluation_result.selected_geometric_solution
Record each finding, missing input, evidence reference, rule version, and untested domain.
receipts[]
CIS v0.1.3 defines mating through the connection plane, sides, ports, tolerances, signatures, and compatibility. The sample CIS identifiers on this page are illustrative.
The session proposed a reusable identity for a resolved connection condition. Its name, derivation, owner, registry, and version policy remain working-group decisions.
Data-derived technical atlas
These drawings are generated from the versioned reference package. Exact envelopes and declared zones are separated from ghosted component anatomy so the page does not imply fabrication detail that the source files do not contain.
Occupied envelopes, candidate-side footprints, attachment zones, access zones, keep-out zones, penetration and obstruction observations, interface-local ports, and reported dimensions.
Bracket profiles, fastener count and spacing, rebar, CLT ply build-up, steel section shape, panel internals, and a shared candidate-to-product placement transform.
Interactive 3D condition viewer
The same package records rendered as a live 3D scene. Every translucent box is an exact declared value: candidate footprints, required access, keep-outs, authorized penetrations, the CIS envelope, and its port datums. Solid components are symbolic anatomy only.
Loading the interactive scene.
Product occupied envelopes, candidate two-sided footprints, required access zones, keep-out zones, authorized penetration zones, the CIS side envelope, and interface-local port datums, all in declared millimeters.
Mullions, glazing, laminations, beam profile, brackets, and fasteners are illustrative shapes. The assembled composition is a coordination view. The package declares no verified shared frame and no candidate-to-product transform.
Interactive case lab
Choose a material branch and a disposition. The plain-language result and JSON are two views of the same simulated record.
The current CTO/CIS mating checks and geometry screens pass. Both simulated concrete connector candidates remain eligible, and the cast-in channel ranks first. No engineering domain ran.
| Connector type / candidate | Applicability and gates | Score | Rank | Selection |
|---|
Variable and ownership map
The first exercise should expose enough detail to test boundaries, while keeping proposed fields separate from current draft requirements.
| Variable | Example | Primary home | Authority | Why it matters |
|---|---|---|---|---|
| panel_system | unitized_curtain_wall in the v0.1.0 panel CTO |
CTO product property | Current CTO field pattern | This package models one curtain-wall panel. Framed wall-panel systems require a separate future product and scenario branch. |
| frame_condition | Not declared in the v0.1.0 package | Candidate future CTO or project-context field | Open decision | Single-stud, double-stud, mullion, and perimeter-frame conditions must not be inferred from this package. |
| edge_condition | concrete_slab_edge, clt_floor_edge, steel_frame_slab_support |
Support CTO subcategory plus scenario branch | Materialized values | Selects one of the package's three substrate branches and its two candidate records. |
| location_condition | Not represented in v0.1.0 | Candidate future project-context field | Open decision | Exterior edge, interior line, opening edge, and return conditions need an explicit future field. |
| connection_role | panel_side ↔ substrate_side; product-local back face ↔ front face |
CTO interface role and CIS side | Current concept | Confirms complementary orientation at the connection plane. |
| substrate.material | reinforced_concrete, clt, structural_steel |
Support product declaration | Typed value | Selects the material-specific applicability branch and evidence requirements. |
| cis_ref + side + port | Illustrative CIS instance, side A/B, structural port cluster | CTO reference and CIS | Current specification | Lets software validate shared standard, side complementarity, port geometry, tolerance, and signature. |
| geometry.plane_gap_mm + normal_misalignment_deg + anchor_zone_overlap_ratio | Valid records use 3 mm, 0.8 deg, and 0.98 | Project-context facts evaluated at geometry_mating | Materialized values | These exact values drive the package's geometry-stage status and interface receipt. |
| geometry_solution.required_access_zone_mm + access_zone_clear | Candidate requirement plus selected-solution boolean | Connector catalog and evaluation result | Materialized values | The page reports the exact selected footprint, offset, access status, and protected-zone status. |
| interface_family_ref | WG-CW-SLAB-EDGE-001 for all nine scenarios |
Working project-context reference to the material-neutral CIS projection | Not normative | The single working wrapper does not replace current CIS mating and does not choose a material-specific connector. |
| connector_type | Adjustable bracket, plate, strap, or clip | Connector catalog | Catalog layer | First filters the type, then selects an eligible product inside that type. |
| evidence[] | Geometry declaration, supplier data, test report reference, qualified calculation reference | Declaration or project context by source | Open placement | Prevents a number or rule from losing its authority, revision, scope, or provenance. |
| structural / fire / seismic | not_evaluated in the geometry-first phase | Future domain evaluator and receipt | Explicit limitation | Keeps an unperformed analysis from being mistaken for a pass or an information gap. |
Outcome vocabulary
All required inputs for that rule were present. This does not imply that another discipline or the complete assembly is approved.
A known requirement was not satisfied. Scoring cannot rescue a candidate that fails a hard gate.
The correct response is to request the missing input. Missing information is not zero and is not a passing result.
Structural, fire, seismic, air, water, and other engineering checks stay here until an identified method and qualified review are supplied.
Decide whether it is selected, inferred, negotiated, or registered, and who controls its identifier and version.
Decide which references belong in CTO, CIS, the project context, a catalog record, or a receipt.
Agree which conditions always exclude a connector and how an unknown required condition affects eligibility.
Define how a manufacturer can implement a shared condition without exposing internal logic or confidential product data.
Machine and human package
Scope, boundary, walkthrough, assumptions, and open questions for working-group review.
/working-group/files/curtain-wall-slab/README.mdApplication-owned validation shape for declarations, classification, selection, evaluation, and receipts.
/working-group/files/curtain-wall-slab/reference-package.schema.v0.1.0.jsonSimulated families and products with applicability predicates, geometry, evidence, and scoring fields.
/working-group/files/curtain-wall-slab/catalogs/connector-candidates.v0.1.0.jsonConcrete, CLT, and steel branches with valid, invalid, and indeterminate results and explicit limitations.
/working-group/files/curtain-wall-slab/reference-package.v0.1.0.jsonComplete versioned bundle
The page is working-example revision v0.3. The materialized machine bundle begins at v0.1.0. Both lab views project the same embedded source records from that bundle, and the exact versioned files remain available above.
All connector dimensions, tolerances, edge distances, capacities, performance references, score weights, and scenario values in this working example are illustrative unless a source is explicitly identified. They are not structural, facade, fire, seismic, air, water, thermal, acoustic, code, fabrication, or installation approval. Qualified reviewers must confirm the governing criteria and evidence.
