---
title: Construction Methodology — Vault Mirror
created: 2026-05-07
type: index
canonical_source: Airtable LFCS-Operations base, `_methodology_*` tables (see schema cheatsheet below)
---

# Construction Methodology

Cross-job reusable methodology — rate templates, productivity benchmarks, exclusion library, reason-code taxonomy, common misses patterns, concept patterns, pre-pricing-grill template.

## Why this folder exists

Per Stage 4 § 1.3 of the LFCS Pricing Agent investigation. Cross-job hygiene seam separates methodology (queryable across jobs) from operational (per-job/per-client/per-bid).

**T1-fail fallback note:** the original Stage 4 spec proposed a separate `Construction-Methodology` Airtable base. PAT scope on 2026-05-07 cannot list workspaces (precondition for `create_base`), so methodology tables live alongside operational tables in the existing `LFCS-Operations` base (`appE43UvTyARe5oJs`) with the `_methodology_*` table prefix. This vault folder mirrors them. Migration to a separate base is trivial later if Rocky decides to split.

## Airtable schema cheatsheet (methodology tables only)

| Table | Airtable ID | Vault mirror |
|---|---|---|
| `_methodology_Element_Taxonomy` | `tblDg9GpOdpYxcbTk` | `element-taxonomy.md` |
| `_methodology_Reason_Code_Taxonomy` | `tblt6UKtvUR91yS5u` | `reason-code-taxonomy.md` |
| `_methodology_Concept_Patterns` | `tblZO2Xd6ptyn4Ix2` | `concept-patterns/*.md` |
| `_methodology_Common_Misses_Patterns` | `tbla5FNdVt2jpI9Fw` | `common-misses-patterns/*.md` |
| `_methodology_Pre_Pricing_Grill_Templates` | `tblGO7F1bCFvrQZL5` | `pre-pricing-grill-template.md` |
| `_methodology_Productivity_Benchmarks` | `tblxfJcdJ9hu8Pqf7` | `productivity-benchmarks/*.md` |
| `_methodology_Rate_Templates` | `tblZjsFrLp0AJwLDw` | `rate-templates/*.md` |
| `_methodology_Exclusion_Library` | `tblzrBAVpgvTzLxjZ` | `exclusion-library/**/*.md` |

## Cross-job hygiene rule (Stage 4 § 2.1)

A row lives in `_methodology_*` if and only if it is queryable across two or more jobs without job-specific operational data attached. Otherwise it lives in operational tables (Jobs / Bids / Bid Line Items / Bid Line Item Overrides / Commercial Events).

Methodology may *reference* operational data via link fields. Operational must NOT directly reference methodology — operational tables hold a `linked_methodology_template_ref` field which methodology populates via reverse-link or skill at write time.

## Source attribution

Every Rate Template + Productivity Benchmark + Concept Pattern carries a `source_attribution` field (e.g., `[source: friend-vault]`, `[source: liam-hcb-2026-05-06]`, `[source: rocky-rate-card-v1.7]`). Friend-vault sources are read-only-by-policy: derive templates, never copy verbatim.