Inputs, outputs, integrations, and control boundaries.
This public documentation index explains what each Matechi product consumes, what it returns, where users review evidence, and which decisions remain with the client team.
QA/QC Agent
Inputs: Revit model data, approved standards, specifications, and rule packs. Outputs: cited findings, element links, applicability context, autofix previews, review decisions, and run reports. Reviewer authority governs every consequential correction.
Clash Detection Agent
Inputs: current and linked models, clash tests, clearance rules, system priorities, and discipline ownership. Outputs: prioritized conflicts, selected 3D evidence, constrained resolution options, fix queues, issue context, and RFI paths.
Modular Configurator
Inputs: approved components, interface rules, option dependencies, prices, and product metadata. Outputs: validated 3D configuration, connection record, live price, bill of materials, and portable configuration package.
Factory Designer and Pod Traveler
Factory Designer compares calibrated production scenarios. Pod Traveler retains unit-level hold points, quality evidence, issues, custody, delivery, installation, and closeout status.
Revit Content Creator and Enablement
Content Creator develops and validates parametric family output from product information. Enablement OS compares candidate agents by value, evidence, access, exceptions, reversibility, and authority.