fix: close audited CAD delivery gate gaps
This commit is contained in:
@@ -25,14 +25,14 @@ Before modeling, write `scope_manifest.json` from the user request and source in
|
||||
"mode": "campus",
|
||||
"requested": ["1#", "2#", "3#"],
|
||||
"buildings": [
|
||||
{"id": "1#", "status": "PASS", "artifacts": ["outputs/1/model.glb"]},
|
||||
{"id": "1#", "status": "PASS", "artifacts": ["../../outputs/1/model.glb"]},
|
||||
{"id": "2#", "status": "BLOCKED", "reason": "unresolved XREF", "artifacts": []}
|
||||
],
|
||||
"site": {"status": "PASS", "artifacts": ["outputs/site_top.png", "outputs/site_manifest.json"]}
|
||||
"site": {"status": "PASS", "artifacts": ["../../outputs/site_top.png", "../../outputs/campus.glb"]}
|
||||
}
|
||||
```
|
||||
|
||||
Every `requested` ID must have exactly one ledger entry. `PASS` requires at least one existing non-empty artifact. `BLOCKED` requires a concrete reason and makes the overall campus result `BLOCKED`, not complete. The campus site must likewise be `PASS` with artifacts. Feed the ledger to `cad_showcase.py run --scope-manifest ...` or `verify_delivery.py --scope-manifest ...`.
|
||||
Every `requested` ID must have exactly one ledger entry and there may be no unrequested extras. `PASS` requires at least one verifiable model artifact: a GLB with mesh primitives, a Blender file with a valid header, or a schema-valid `building_spec.json`; an arbitrary non-empty text/JSON file does not satisfy scope. Campus site evidence must include a valid model or readable image. Relative paths resolve from the scope manifest's directory. `BLOCKED` requires a concrete reason and makes the overall campus result `BLOCKED`, not complete. Feed the ledger to `cad_showcase.py run --scope-manifest ...` or `verify_delivery.py --scope-manifest ...`.
|
||||
|
||||
## Placement Evidence
|
||||
|
||||
@@ -64,6 +64,8 @@ Use `assemble_campus.py` with per-building `rotation_deg` where needed. Require:
|
||||
- a top-view overlay or render showing each model inside its site outline;
|
||||
- numeric envelope dimensions and neighbour gaps in the notes/evidence.
|
||||
|
||||
Do not classify a small gap from distance alone. Corroborate a 0.15-0.30m attached-building/expansion-joint interpretation with the neighbour roof shown on the subject building's roof plan and matching floor elevations. A negative gap is always a placement error. A multi-metre hypothesis that pushes either building through the red line is also wrong.
|
||||
|
||||
`--allow-overlap` is for a documented shared structure or verified interlocking geometry, not a shortcut around placement bugs.
|
||||
|
||||
## Site Context
|
||||
|
||||
Reference in New Issue
Block a user