VASUNDHARA · COST INTELLIGENCE

Methodology & Assembly Audit

A live technical view of the 28-assembly production architecture. This page reads the canonical methodology-binding, dependency and rate-analysis registries directly. It distinguishes methodology identification from vocabulary reconciliation, component evidence, execution evidence and final production release.

FAIL-CLOSED RULE: a resolved methodology is not a production rate. Composite dependencies, contextual selections, component evidence, productivity evidence and project cross-checks remain independently gated.

Architecture

The release chain

01Methodology
02Vocabulary
03Component / system evidence
04Execution + commercial evidence
05Production gate

28 assemblies

Assembly-level status

The status below is calculated from the canonical registry rows. “Resolved dependency” means the authoritative dependency methodology has been identified; it does not mean the dependency is production-ready.

AssemblyMethodologyMapping stateRolesOpen production blockers

Methodology roles

Vocabulary reconciliation ledger

The reconciliation layer now distinguishes exact catalogue-role correspondence from composite roles that must not be collapsed into atomic inputs, and from roles for which no safe equivalence has been established.

AssemblyMethodology roleDependency classBindingVocabulary reconciliationProduction treatment