Русская версия

Checkpoint: NO_GO

Samolet TechLab Task 07 is not ready for customer sign-off. Open blockers: RT-001 (customer accuracy corpus), RT-002 (approved norm pack), RT-003 (federated MEP scope) — see audit/reports/CRITICAL_BLOCKERS.md. Claims SSOT: audit/reports/CLAIMS_LOCK_2026_07_17.md · verified vs planned: docs/pilot-claim-boundary-2026.md · Tier-0 docs: docs/TIER0_INDEX.md · verdict ownership: docs/architecture/ADR-001-verdict-ownership-2026.md. Forbidden until evidenced: product accuracy >90%, DWG-ready, MEP delivered, CDE-ready BCF, independent calc correctness.

Open-source acceptance-criteria assistant for openBIM packages (IFC + IDS + cross-document evidence).

AeroBIM runs a deterministic Shared-gate style check (ISO 19650 framing: evidence for Shared, not contractual Published authorization). It fuses IFC property/quantity checks, IDS, drawings, and calculation text into a single report with explicit capability honesty, finding provenance, and BCF ZIP export. Independent CDE import and customer accuracy claims remain out of scope until evidenced. Architecture SSOT: docs/architecture/TARGET_HYBRID_ARCHITECTURE_TZ_2026.md.

What works: project-package analyze; IFC/IDS/cross-doc; summary.passed Shared-gate (ADR-001); pilot/production fail-closed profiles; ACL 404; SSRF outbound guard; provenance stamp/persist; BCF 2.1/3.0 structural ZIP; HITL review-events; evidence bundle CLI (python -m aerobim.tools.export_evidence_bundle); pytest / vitest counts SSOT via runtime baseline (frontend.tests_passed when recorded; else see baseline/CI).

Experimental: OpenCDE BCF API push; BCF 3.0 consumer path; optional clash/OCR extras; IFC KG advisory scaffold.

Available (eng): PackageOutcome on summary.outcome (pass / pass_with_warnings / review_required / blocked / failed); run manifest + reproducibility hash; stage timeout budgets.

Planned: Stage-3 finding field expansion; profiling-driven performance wave.

Needs customer: RT-001 accuracy corpus · RT-002 approved norms · RT-003 federated MEP (CRITICAL_BLOCKERS).

Not claimed: product accuracy >90%; customer ≤30 min SLA; native DWG; MEP system clash delivered; independent calc correctness; CDE-ready BCF. See capability-claim-matrix · PROJECT_STATUS_AUDIT · pilot-protocol · benchmark-evidence.

Statuses below are repository / fixture capabilities unless marked otherwise. Optional extras and fail-closed policies govern whether a green summary.passed is honest.

All three releases pass through the same IfcOpenShellValidator and IfcTesterIdsValidator adapters. Pset/property name divergence between releases is surfaced as a ValidationIssue rather than a silent skip. IFC2x3, IFC4, and IFC4x3 fixture files live in samples/ifc/. See docs/ifc-compatibility-matrix.md for the formal compatibility matrix and per-feature degradation rules.

Canonical taxonomy: docs/architecture/BCF_EVIDENCE_LADDER_T0_T4_2026_07.md.

Allowed: structural ZIP AVAILABLE. Forbidden until T2: “BCF ready for CDE”, “CDE interoperable”.

Iteration B.1 has started with a compatibility-first storage foundation:

• ObjectStore domain port for binary artifacts (put/get/delete/presign);
• LocalObjectStore for current local/runtime flows;
• S3ObjectStore for S3/MinIO-compatible buckets via optional enterprise extras;
• PostgresAuditStore foundation that adds a Postgres report-summary index while keeping full payload round-tripping on the existing JSON/object path;
• AEROBIM_REPORT_TTL_DAYS retention knob for persisted report payloads.

Current behaviour is intentionally safe-by-default:

• without enterprise extras, AeroBIM keeps working with local storage;
• when AEROBIM_DB_URL and enterprise dependencies are available, report summaries are indexed in Postgres;
• IFC source binaries and persisted drawing previews are stored behind the ObjectStore abstraction, so S3/MinIO rollout no longer requires HTTP contract changes.

# Clone
git clone https://github.com/KonkovDV/AeroBIM.git
cd AeroBIM/backend

# Create virtual environment
python -m venv .venv
source .venv/bin/activate  # Linux/macOS
# .venv\Scripts\activate   # Windows

# Install
pip install -e ".[dev,raster]"

# Optional extras
# pip install -e ".[clash]"    # enable geometry clash detection
# pip install -e ".[docling]"  # enable non-text document extraction
# pip install -e ".[enterprise]"  # enable S3/Postgres enterprise storage adapters

# Run tests
pytest tests -q

# Extraction quality gate (Russian AEC corpus)
python -m aerobim.tools.evaluate_extraction --min-macro-f1 0.70
python -m aerobim.tools.evaluate_detection_precision \
  --labels ../samples/benchmarks/detection-precision/labels-synthetic.json \
  --detections ../samples/benchmarks/detection-precision/detections-synthetic.json \
  --min-precision 0.6 --min-recall 0.6 --min-f1 0.6

# Seed one deterministic runtime smoke report
python -m aerobim.tools.seed_smoke_report

# Or run the full live review smoke chain in one command
python -m aerobim.tools.run_live_review_smoke

# Or run the baseline throughput rail against the representative benchmark pack
python -m aerobim.tools.benchmark_project_package --iterations 1 --warmup-iterations 0

# Or run the second fire-compliance benchmark profile explicitly
python -m aerobim.tools.benchmark_project_package --pack ../samples/benchmarks/project-package-fire-compliance.json --iterations 1 --warmup-iterations 0

# Or run the stress multisource benchmark profile explicitly
python -m aerobim.tools.benchmark_project_package --pack ../samples/benchmarks/project-package-stress-multisource.json --iterations 1 --warmup-iterations 0

# Start server
python -m aerobim.main
# → http://127.0.0.1:8080/health

Before pushing to main, run the same baseline checks used by CI:

cd AeroBIM/backend
python -m ruff format --check src tests
python -m ruff check src tests
python -m mypy src
pytest tests -q

If ruff format --check reports files to reformat, run:

python -m ruff format src tests

Verified capabilities are backed by tests, API contracts, or persisted report artifacts. Planned / missing contours (DWG, human CV, MEP system clash, calculation correctness, customer accuracy) are explicit on GET /v1/system/capabilities and in the Claims Lock.

cd backend
python -m aerobim.tools.benchmark_project_package --iterations 1 --warmup-iterations 0
python -m aerobim.tools.measure_package_sla --corpus-kind fixture
python -m aerobim.tools.verify_bcf_structural_handoff
python -m aerobim.tools.run_ablation_study
python -m aerobim.tools.generate_benchmark_report --output-dir ../docs/evidence
python -m aerobim.tools.export_runtime_baseline
python -m aerobim.tools.export_evidence_bundle \
  --pack ../samples/benchmarks/project-package-techlab-demo.json \
  --output ../artifacts/evidence-bundle/techlab-demo

Throughput and F1 figures are environment-specific and fixture-scoped unless corpus_kind=customer and adjudication gates pass. Publish pack paths, CLI flags, machine fingerprint, and artifact hashes with any performance claim. Cite via CITATION.cff or docs/CITATION.bib.

| GET | /v1/system/capabilities | Static honesty surface (DWG/CV/MEP/calculation claim boundary) | | GET | /health | Readiness probe | | POST | /v1/validate/ifc | Validate IFC against requirements + IDS | | POST | /v1/analyze/project-package | Multimodal validation (spec + calc + drawing + IDS + IFC) | | POST | /v1/analyze/project-package/reinforcement-digest | OpenRebar provenance digest (сверка labels; not correctness verification) | | POST | /v1/analyze/project-package/submit | Accept a same-process background analysis job for larger packages | | GET | /v1/analyze/project-package/jobs/{job_id} | Poll async project-package job status | | POST | /v1/uploads | Multipart document ingest; returns storage-relative path for analyze | | GET | /v1/reports | List persisted reports with optional project, discipline, and passed filters | | GET | /v1/reports/{id} | Get report by ID | | POST | /v1/reports/{id}/review-events | Append HITL review telemetry (does not affect pass/fail) | | GET | /v1/reports/{id}/review-events | List review events for a report | | GET | /v1/reports/{id}/review-kpi | Aggregate triage/acceptance KPIs | | GET | /v1/reports/{id}/source/ifc | Download the report-scoped IFC source for browser viewing | | GET | /v1/reports/{id}/drawing-assets/{asset_id}/preview | Download a report-scoped drawing preview for 2D evidence overlays | | GET | /v1/reports/{id}/export/json | Download JSON export | | GET | /v1/reports/{id}/export/html | Download HTML export | | GET | /v1/reports/{id}/export/bcf | Download BCF 2.1 ZIP by default; use ?version=3 for BCF 3.0 |

POST /v1/analyze/project-package also supports optional OpenRebar provenance fields:

• reinforcement_report_path: path (inside AEROBIM_STORAGE_DIR) to an OpenRebar canonical *.result.json report;
• reinforcement_source_digest: expected SHA-256 digest for report provenance fingerprint checks.
• reinforcement_waste_warning_threshold_percent: optional waste threshold (percent) for coordination warnings.
• reinforcement_provenance_mode: advisory (default) or enforced to escalate OpenRebar provenance warnings into blocking errors.

Use /v1/analyze/project-package/reinforcement-digest to generate reinforcement_source_digest directly from a stored OpenRebar report before calling project-package analysis.

For offline or CI shell workflows, use:

python -m aerobim.tools.openrebar_provenance_digest <path-to-openrebar-result.json>

When provided, AeroBIM adds cross-document warnings if:

• OpenRebar report contract ID is unexpected;
• OpenRebar optimizer indicates fallback master solver usage;
• OpenRebar master-problem strategy does not indicate a HiGHS-backed path;
• project context mismatches (project_name vs metadata.projectCode);
• supplied provenance digest does not match report fingerprint.
• reported summary.totalWastePercent exceeds the configured warning threshold.

Five-layer Clean Architecture with strict inward dependency direction:

core/          DI container, tokens, config (no project imports)
domain/        Immutable models, Protocol ports, logging contract
application/   Use case orchestration (requirement fusion, cross-doc detection)
infrastructure/ Adapters: IfcOpenShell, IfcTester, Docling, IfcClash, BCF, filesystem
presentation/  FastAPI HTTP API, correlation middleware

Infrastructure now also includes an artifact ObjectStore seam plus an optional Postgres summary-index adapter for Iteration B.1.

20 domain ports → 30 infrastructure adapters → 28 DI tokens — all wired in a single composition root (bootstrap_container()). Report payloads include an explicit capabilities object (ok / skipped / failed) so optional engines (clash, IDS, unit scale, raster, schema) cannot silently look like a clean PASS. Any FAILED capability forces summary.passed=false.

All settings are read from environment variables (see backend/.env.example):

aerobim/
├── backend/                 # Python FastAPI backend (see generated baseline below)
│   ├── src/aerobim/         # Source: core → domain → application → infrastructure → presentation
│   ├── tests/               # Backend test suite (see generated baseline below)
│   └── pyproject.toml
├── clients/revit-plugin/    # Thin authoring-side client boundary (planned)
├── docs/                    # TechLab jury docs only (see docs/README.md)
├── frontend/                # Browser review shell
├── audit/                   # Claims lock, blockers, citeable honesty fixtures
├── samples/                 # IFC, IDS, drawing, spec fixtures
├── .github/workflows/       # CI pipeline (lint, typecheck, test, benchmark-smoke) + manual release-readiness gates
└── LICENSE                  # MIT

Backend src ~35544 LOC; tests ~25971 LOC; 1138+ test functions; extraction macro_f1=0.8600000000000001 (fixture corpus; not product accuracy)

Public GitHub is the TechLab jury pack only: code + TZ / claims / architecture. Operator runbooks, Red Team dumps, and archive stay in .local/ (not published).

Use scripts/git_commit.ps1 or the VS Code task AeroBIM: commit (single author) so history stays single-author without Co-authored-by trailers. Enable the repo hook:

git config core.hooksPath .githooks

Suggested repo About — .github/repository-metadata.md.

• Contributing
• Security Policy
• Citation Metadata
• Support
• Maintainers
• Release Policy

Use the manual GitHub Actions workflow .github/workflows/release-readiness.yml when preparing a release candidate.

It runs benchmark rails by default and can optionally run the full live review smoke harness with browser artifacts. The live-smoke path now installs Playwright and Chromium inside the workflow job so browser capture is reproducible in CI. Main CI benchmark-smoke runs now also emit a compact benchmark summary table in workflow output and artifacts. When needed, require_live_smoke_gate=true enforces live-smoke execution as a mandatory policy gate for that release-readiness run. CI benchmark-smoke now also runs advisory threshold evaluation from samples/benchmarks/benchmark-thresholds.json and publishes the threshold summary alongside benchmark artifacts. Release-readiness benchmark rails now support benchmark_threshold_mode (advisory or enforced) plus explicit threshold profile path selection.

• Python 3.12+, FastAPI, Uvicorn
• IfcOpenShell / IfcTester / IfcClash (buildingSMART toolchain)
• web-ifc + Three.js for browser-side IFC review
• PyMuPDF for deterministic PDF text; RapidOCR only when .[raster] is installed
• Docling (optional, document parsing)
• 5-layer Clean Architecture, constructor DI, Protocol ports

MIT