Generated: 2026-06-22 Client: Moreton Bay Regional Council Local fixture standard: ADAC 4.2 Production standard rule: confirm the project/client accepted ADAC version and capture guideline before production acceptance. Purpose: Turn the ADAC research and local MRBC evidence into a concrete CSM/macro proof target.

• Output/MRBC/MRBC_attribute_schema.json: MRBC asset classes, geometry families, mandatory attributes, source sections, and positional notes extracted from the MRBC guideline.
• Output/MRBC/MRBC_attribute_choices.json: currently captured choice lists; known incomplete until the ADAC 4.2 Data Dictionary XLS is available.
• Output/MRBC/MRBC_validation_report.md: current mapping/validation state.
• Output/MRBC/MRBC_mapfile.json: Veris code and subtype to MRBC/ADAC asset-path candidates.
• Output/MRBC/MRBC_mapping_report.md: mapping evidence and open questions.
• IPWEA-QNT ADAC public page: ADAC is the public-works asset data specification/business process for consistent asset data capture and transfer.
• Moreton Bay ADAC public page and submission guidelines: ADAC XML is part of the as-constructed handover package; the accepted version/capture rules are client/project context, not a universal default.
• 12d ADAC module/manual/training material: 12d reads/writes ADAC XML and treats data preparation as a first-class workflow before report/XML generation.
• 12d ADAC training workflow: examine the ADAC XML schema, understand ADAC assets in 12d, create/apply Metaconnex and custom attributes, assign ADAC assets to points/lines/polygons, bulk edit asset features, validate assets, create the ADAC header, generate the report/XML, and read XML back for proof.

• Classes/rows in validation report: 77
• Ready mapped rows: 65
• Calculation rows without strategy: 0
• Calculation rows with assigned formula/reference strategy: 8
• Missing-strategy rows: 0
• Asset-class rows covered by subtype strategy: 4
• Validation report totals: 1488 expected attributes, 1416 captured, 1403 mapped, 9 calculation-pending attributes, 85 missing attributes.

For each selected fixture group, CSM must prove: selected 12d source model -> group/code identity -> ADAC asset path -> geometry family -> mandatory attributes -> choice values -> source-kind/apply method -> independent validation result.

Group bulk writes are only accepted when the fixed macro leaves evidence rows showing group, attribute, value, and affected element count, then an independent inspector confirms the attribute storage.

12d ADAC proof is not just a schema-valid XML file. The 12d-side proof path must keep these stages separate and evidenced:

• Project/header context exists for the ADAC job, including the client/project version decision.
• Source model selection is explicit and points at real 12d asset geometry, not placeholder/demo rows.
• Feature/group scan resolves the CSM code to an ADAC asset path and geometry family, matching the ADAC asset concept used by 12d rather than only a survey code label.
• Metaconnex/custom-attribute readiness is explicit: CSM must know which ADAC feature prompt/output/attribute path each group and attribute maps to before writing values.
• ADAC assets can be assigned to the correct geometry families: points, lines, and polygons are not interchangeable proof.
• Mandatory and conditional attributes are either field/source backed, project values, safe group bulk values, or formula/reference derived.
• Bulk editing is controlled: group-wide values such as comments can be applied deliberately, while unique field values are preserved unless the operator overrides them.
• Choice values are checked against the client/dictionary source where available; missing dictionary proof remains a blocker, not a pass.
• Macro write evidence records group, attribute/path, source mode, value, affected/skipped counts, and output evidence path.
• Independent inspection reads the resulting 12d attribute storage and compares expected vs actual values.
• 12d ADAC validation/report/XML/read-back is a later proof layer and must distinguish XSD validity, client capture-rule validity, and real project asset completeness.

CSM app proof must mirror the same contract: confirmed ADAC-delivery scope rows need standard_version and capture_guideline_source, runtime profiles need real project references, and validation reports must not turn a zero-asset ADAC shell into production acceptance.

These rows now have a data-prep strategy. They still require live macro execution and independent inspector evidence before final production ADAC acceptance.

These are suitable first candidates for a 12d fixture/import/apply/inspect proof because the current mapping report shows no missing attributes.

• Obtain or locate the ADAC 4.2 Data Dictionary XLS for missing enum choices, or record that choice proof is blocked.
• Pick one ready-mapped point, line, and polygon row from this matrix and create/import representative 12d source elements.
• Run the fixed CSM macro against the selected source model and Project Runtime Profile.
• Use group bulk on a safe office/comment attribute and verify the macro evidence row plus independent 12d attribute readback.
• Validate required attributes/choices against the MRBC matrix before claiming ADAC readiness.

Use Output/MRBC/MRBC_validation_report.md for the full 77-row validation table and per-attribute detail.