NC-METH-001 v1.1 — Part F: Governance¶
Change-Control · Acceptance Tests · Regulatory Monitoring · Annual Recalibration · Segment-ID Consolidation · Deprecations · Storage¶
12 May 2026 · Internal · Authors: AI-assisted, M. Forni / S. Rubinyi review
F.0 Overview¶
Part F is the governance section of the methodology. It closes the document at v1.1.0 by specifying how subsequent versions are produced, reviewed, locked, and distributed.
Without governance, a methodology document becomes static prose that drifts from operational reality. The audit cycle (NC-MN-001-R1/R2/R3) was the corrective for exactly that drift: 47 register items, 23 of them active gaps where the model, the IC paper, the segment register, and the memory had diverged from each other. Governance is what prevents the next drift cycle.
Eight governance modules:
| Module | What it does |
|---|---|
| F.1 Change-control protocol | Semver application, change log, approval workflow |
| F.2 Acceptance test suite | pytest-based test suite (closes AUDIT-034) |
| F.3 Regulatory monitoring | Six external sources tracked with named monitors |
| F.4 Annual recalibration | Rolling annual refresh of time-sensitive parameters |
| F.5 Segment-ID consolidation | V3 IDs deprecated; v1.0 register IDs canonical |
| F.6 Deprecation handling | Deprecation warnings, sunset timelines, retired artefacts list |
| F.7 Document storage and Git | Drive + Git, naming conventions, distribution |
| F.8 v1.1.0 lock gating events | Specific items that must close before v1.1.0 lock |
Part F is written for Steven Rubinyi (COO) and Marc Forni (CEO) as the methodology's joint approvers, with the Investment Committee notified for MAJOR version events.
F.1 Change-control protocol¶
F.1.1 Semver applied¶
Per Part A § A.5.1, NC-METH-001 uses standard semver: vMAJOR.MINOR.PATCH. Part F operationalises this.
Current version target: v1.1.0 (this document family in progress). Prior version: v1.0 baseline locked 9 May 2026.
F.1.2 Version-bump triggers¶
PATCH (v1.1.0 → v1.1.1) — documentation refinement that does not change calculation outputs:
| Triggers | Examples |
|---|---|
| Typo correction, citation update, formatting | "Capital IC" → "Capital IQ" |
| Clarification of an existing convention | Y1 calendar-year disambiguation (per A.7 gap #5) |
| Reference update (e.g., new audit register version) | R3 v0.3 → R3 v0.4 |
| Cross-reference fix | Part D ↔ Part C consistency |
Threshold: no calculation output changes more than ±50 bps IRR or ±5% CAPEX at any estate.
MINOR (v1.1.0 → v1.2.0) — substantive methodology change with calculation impact:
| Triggers | Examples |
|---|---|
| New parameter or refined value affecting model | LFP cost curve update from BNEF 2027 |
| New typology added beyond the six | (Hypothetical: rooftop floating PV variant) |
| New estate-specific adjustment generalised | C4 corrosion premium calibration per AUDIT-002 closure |
| Pipeline stage refinement | Confidence scoring algorithm formalised |
| Annex addition (Annex G, H, I, J) | Per-tenant credit framework live |
Threshold: calculation outputs change between ±50 bps and ±200 bps IRR; or between ±5% and ±20% CAPEX at any estate; or new methodology capability.
MAJOR (v1.x.y → v2.0.0) — structural change requiring full re-validation:
| Triggers | Examples |
|---|---|
| Pipeline restructure (B.1–B.10 reorganised) | (Hypothetical: per-segment yield modeling absorbed into B.4) |
| Typology taxonomy change (six → seven typologies, or merger) | (Hypothetical: T4A and T4B-DC merged as T4) |
| Confidence taxonomy change | HIGH/MEDIUM/LOW/ASPIRATIONAL boundaries revised |
| Financial structure shift | Project-finance abandoned in favour of corporate-finance |
| FX convention change | Multi-currency basis introduced |
Threshold: calculation outputs change more than ±200 bps IRR or ±20% CAPEX at any estate; or fundamental restructure of methodology framework.
F.1.3 Change-log format¶
Every version update creates a change-log entry in methodology-package/CHANGELOG.md:
## v1.1.0 (target: per Part F.8 lock)
**Date locked**: [TBD per WP1-WP5 closure]
**Approver(s)**: M. Forni + S. Rubinyi
**Changes**:
- Part A (framing): new document; canonised conventions
- Part B (pipeline): new document; canonised 10-stage flow
- Part C (typologies): new document; 6 per-typology specs canonised
- Part D (cross-cutting): new document; 9 module specs canonised
- Part E (runbook): new document; 6 operational stages canonised
- Part F (governance): new document; this document
- Annex G (per-tenant credit framework): new; closes AUDIT-027
- Annex H (LC-specific cost driver documentation): new; closes AUDIT-040; gating event
- Annex I (pytest acceptance test suite): new; closes AUDIT-034
- Annex J (audit register live document): new; closes AUDIT- ranges 001-047
- Tests: full pytest suite implemented per F.2
**IRR impact summary**: LC sponsor IRR at 52% LTV
- v1.0 baseline: 12.2%
- v1.1 target: 12.2% ± 50 bps depending on WP1 (yield), WP2 (LC-specific cost), WP4 (OPEX) closures
- Net direction expected: +0 to +30 bps if WP1 reconciles to higher of two values; −30 to −80 bps if WP1 reconciles to lower
**Closed register items**: AUDIT-001 / AUDIT-014 / AUDIT-016 / AUDIT-040 / AUDIT-041 (high-materiality five); plus 10 governance items per R3 register.
## v1.0 (9 May 2026 baseline)
**Date locked**: 9 May 2026
**Approver(s)**: M. Forni
**Changes**: baseline assemblage of pre-existing methodology artefacts
**IRR impact summary**: LC sponsor IRR at 52% LTV: 12.2% (canonical)
**Closed register items**: n/a (baseline)
F.1.4 Approval workflow¶
Per Part A § A.5.3, formalised here:
| Version type | Required approvers | Subject-matter review | Test suite |
|---|---|---|---|
| PATCH | M. Forni OR S. Rubinyi (single) | None required | Advisory pass |
| MINOR | M. Forni AND S. Rubinyi (both) | Relevant SME owner (per topic) | All tests pass |
| MAJOR | M. Forni AND S. Rubinyi (both) + IC notification | All SMEs (yield, carbon, financial, regulatory, risk) | All tests pass + re-validation of all estate IC papers |
SME assignments (per Part E § E.8 + memory):
| Topic | SME |
|---|---|
| Yield, modeling, financial model construction | Steven Rubinyi |
| Carbon | Chandra Sinha |
| Financial structure, debt sizing | Jin Yong |
| Regulatory, in-country, IEAT | Kwan Suddhi-Dhamakit |
| Risk, AUDIT register, insurance | Benedikt Signer |
F.1.5 Pre-merge review process¶
For MINOR and MAJOR changes:
- Draft proposed change → branch in Git (or working draft in
methodology-package/_drafts/) - Run acceptance test suite (per F.2) — all tests pass before review
- SME review — relevant SME(s) approve via comment / sign-off
- Joint approver review — Marc + Steven approve via change-log signature
- Lock — merge to main; CHANGELOG entry; tag version in Git; refresh Drive canonical
- Distribute — notify IC and Fund I LPs (for MAJOR); notify team (for MINOR); silent (for PATCH)
PATCH versions skip steps 3–4 but still require step 2 (test suite) and steps 5–6 (lock + distribute).
F.2 Acceptance test suite (AUDIT-034)¶
F.2.1 Purpose¶
The pytest acceptance test suite verifies that methodology changes do not silently break downstream artefacts (financial models, IC papers, segment registers). It is the closest thing the methodology has to continuous integration.
AUDIT-034 in the R3 register was the gap: methodology v1.0 had no automated tests. Part F closes this by specifying the test suite for v1.1 lock.
F.2.2 Test categories¶
Five test categories (Annex I formalises the per-test spec):
| Category | Purpose | Test count target |
|---|---|---|
| Replication tests | Re-run LC and BP financial models through methodology; assert IRR within ±50 bps of stated values | 4–6 tests |
| Cross-estate ranking | Rank 13 estates by post-mitigation leveraged IRR; assert top-5 ranking stable across cost bands | 1–2 tests |
| High-materiality findings | Each of the 3 ACTIVE-IRR findings (AUDIT-001, AUDIT-014, AUDIT-016) reflected in calibrations with documented closure | 3–5 tests |
| Governance | Semver tag present; CHANGELOG entry exists for current version; deprecated parameters absent; V3 segment IDs absent | 4–6 tests |
| Cross-reference integrity | Part B references Part C correctly; Part D references Part C correctly; Annex references in main text resolve | 2–3 tests |
Total: ~15–22 tests for v1.1.0 lock.
F.2.3 Test execution¶
Test framework: pytest (Python 3.11+).
Location: methodology-package/tests/ (Git-versioned per F.7).
Execution: locally during development; CI on push (when Git repo set up).
Example replication test:
def test_lc_irr_within_methodology():
"""LC sponsor IRR at 52% LTV should match methodology canonical ±50 bps."""
inputs = load_inputs_from_segment_register("NC-IS-LC-001_v1.0.csv")
debt_size = solve_lender_sized_debt(inputs, target_dscr=1.05, p_level="P90")
irr = compute_sponsor_irr(inputs, debt_size, contract_tenor=25)
assert 11.7 <= irr <= 12.7, f"LC IRR {irr}% outside ±50 bps of canonical 12.2%"
F.2.4 Pass/fail criteria per version bump type¶
| Version type | Test suite requirement |
|---|---|
| PATCH | Advisory pass — failures documented but not blocking |
| MINOR | All tests pass — blocking for lock |
| MAJOR | All tests pass + re-validation of all estate IC papers — blocking |
F.2.5 Test artefacts¶
The test suite produces:
- test_report.html — full test results with timestamps
- test_coverage.json — coverage by methodology section (which parts of Parts A–F are exercised by tests)
- regression_log.csv — historical pass/fail tracking across versions
These artefacts are committed to Git on each test run.
F.3 Regulatory monitoring¶
F.3.1 Six monitored sources¶
Per memory and prior conversation, six external sources are tracked with named monitors:
| Source | Watches for | Frequency | Named monitor |
|---|---|---|---|
| TGO (Thai Greenhouse Gas Management Organization) | Grid emission factor revisions; carbon mechanism guidance | Quarterly + on-publication | Chandra Sinha |
| BOI (Board of Investment) | Activity 5.2.1 changes; EEC 13-yr enhancement decisions; new categories | Quarterly + on-publication | Kwan Suddhi-Dhamakit |
| EEC (Eastern Economic Corridor Secretariat) | Phase 0 enhancement status; new EEC zone delineations; tax incentive changes | Quarterly | Kwan Suddhi-Dhamakit |
| ERC (Energy Regulatory Commission) | MEA/PEA TOU tariff revisions; demand-charge structure | Annually on tariff publication | Steven Rubinyi |
| ICC (International Carbon Credit Thailand Guideline) | Solar inclusion/exclusion from ITMO/CORSIA; mechanism scope | On-publication (rare) | Chandra Sinha |
| MEA (Metropolitan Electricity Authority) | Tariff schedules; interconnection guidelines; medium-voltage requirements | Annually | Steven Rubinyi |
F.3.2 Update protocol¶
When a monitored source publishes new data:
- Detect: monitor identifies publication
- Assess: monitor evaluates impact on methodology (e.g., grid EF revision affects D.5.5; tariff revision affects D.4)
- Classify: PATCH (no calculation impact) / MINOR (calculation impact within thresholds) / MAJOR (fundamental change)
- Update: monitor drafts the methodology change (or recommends ignoring)
- Review and lock: per F.1.4 approval workflow
- Notify: IC and Fund I LPs for MINOR/MAJOR
The monitor is responsible for items 1–4; F.1.4 governs 5–6.
F.3.3 Annual regulatory monitoring review¶
Each January, the methodology team conducts a regulatory monitoring review: - All six sources reviewed for missed updates - Named monitors confirm or rotate - New sources added if regulatory landscape shifts (e.g., Thai SEC for ITMO market depth) - Output: annual monitoring memo + methodology refresh
F.4 Annual recalibration¶
F.4.1 Rolling annual refresh¶
Each January, the methodology team refreshes time-sensitive parameters. The refresh is itself a MINOR version bump (v1.x.y → v1.{x+1}.0) unless changes are PATCH-level only.
F.4.2 Parameters subject to annual refresh¶
| Parameter | Source | Trend direction |
|---|---|---|
| LFP cost (D.6.4) | BNEF cost curve | Declining ($175 → projected $40–80 by 2035) |
| Solar module pricing (TOPCon $/Wp) | BNEF / supplier quotes | Generally declining |
| FX rate (A.4.1) | BoT (Bank of Thailand) reference | Volatile; methodology refreshes on >5% drift |
| MEA TOU rates (D.4.1) | ERC publication | Generally increasing 2–4%/yr nominal |
| Grid emission factor (D.5.5) | TGO Combined Margin | Generally declining as Thailand grid decarbonises |
| Carbon pricing (D.5.2 / D.5.3) | GS PoA / T-VER market data | Volatile; methodology refreshes on >20% drift |
| Y10 terminal multiple (D.9.1) | Thai infrastructure transaction comps | Generally stable around 12–14× |
| Debt cost (D.7.2) | EXIM / commercial bank pricing | Variable with rate environment |
| OPEX cost layers (D.3.2) | Vendor benchmarks + market data | Generally increasing with CPI |
F.4.3 Emergency updates between annual refreshes¶
Some events trigger mid-year refresh: - BOI policy change (e.g., EEC 13-yr enhancement confirmed/denied) - ICC mechanism scope change (e.g., solar re-inclusion in ITMO) - Major FX shock (>10% drift over a quarter) - BNEF major LFP cost curve revision - Thai regulatory event (e.g., new tariff structure for grid-export)
These trigger MINOR or MAJOR version bump per F.1.2 thresholds.
F.5 Segment-ID consolidation¶
F.5.1 V3 segment IDs deprecated¶
The V3 segment ID scheme (LC-S-V3-XXXX and similar) was used during the Phase 5 / 6 audit cycle and is formally retired in v1.1 per Part A § A.5.5.
F.5.2 v1.0 register IDs canonical¶
The canonical segment ID format is per the LC v1.0 register (NC-IS-LC-001):
Examples:
- LC-T1-01 (LC, T1 rooftop, segment 01)
- LC-T4A-02 (LC, T4A carport, segment 02)
- LC-T6W-03 (LC, T6W canal canopy, segment 03)
- BP-T2-15 (BP, T2 ground-mount, segment 15)
F.5.3 ID stability rules¶
Once assigned, segment IDs are stable across methodology versions:
- Existing IDs are preserved through PATCH and MINOR updates
- New segments get the next sequential NN within their estate-typology
- Retired segments keep their ID but get a "RETIRED" status flag; ID is not reused
- MAJOR version changes may renumber if typology taxonomy changes; preceded by 6-month migration notice
F.5.4 Cross-references¶
Segment IDs are referenced throughout the methodology (Parts B, C, D) and downstream artefacts (IC paper, financial model, segment register). Cross-reference integrity is enforced via F.2.2 test category.
F.5.5 Reserve typology IDs¶
Reserve typologies (T1X / T2X / T6X) use the same format with the "X" suffix:
- LC-T1X-01 for aspirational T1X segments
- Promoted from reserve to active becomes LC-T1-XX with next sequential NN (the original T1X ID is retired)
F.6 Deprecation handling¶
F.6.1 Deprecation lifecycle¶
Parameters and artefacts pass through three states: 1. Active — current canonical 2. Deprecated — replaced by new canonical; old value still referenced in legacy artefacts with deprecation warning 3. Retired — removed from methodology; only present in historical change log
Transition: Active → Deprecated (issued with deprecation warning) → Retired (after sunset period).
F.6.2 Deprecation warnings¶
Computational artefacts (financial models, segment registers, methodology code) should generate DeprecationWarning when deprecated parameters are referenced. Example:
import warnings
OLD_BESS_COST = 400 # per kWh (deprecated)
NEW_BESS_COST = 175 # per kWh + thermal premium
def get_bess_unit_cost(version="current"):
if version == "legacy":
warnings.warn(
"BESS cost $400/kWh deprecated; use $175/kWh + thermal premium per memory edit 16",
DeprecationWarning
)
return OLD_BESS_COST
return NEW_BESS_COST + 12.5 # mid-thermal-premium
F.6.3 Current deprecations (per Part A § A.5.5)¶
| Deprecated | Replaced by | Status as of v1.1.0 |
|---|---|---|
| FX 32 THB/USD unqualified | FX 35 main / 32 IET-only | Deprecated 12 May 2026; retire after v1.2 |
| BESS CAPEX $400/kWh | $175/kWh + thermal $10–15/kWh | Deprecated; retire after v1.2 |
| Grid EF 0.475 / Scope-2 only | 0.4091 TGO Combined Margin | Deprecated; retire after v1.2 |
| ITMO/CORSIA pricing for solar carbon | Excluded per ICC Aug 2025 — GS PoA $15/t base | Deprecated; retired immediately (no fall-back valid) |
| LC P50 yield 1,350 (older artefacts) | 1,380 (model) or 1,485 (methodology) pending AUDIT-001 | Deprecated; sunset on AUDIT-001 closure |
V3 segment ID scheme LC-S-V3-XXXX |
v1.0 register IDs LC-T1-01 etc. |
Deprecated; retire after v1.2 |
methodology-package 2 Google Drive folder |
methodology-package (canonical) |
Deprecated 12 May 2026; folder retire after audit-trail confirmation |
LC envelope 39.1 MWp / 42 segments |
47 segments / 34.59 MWp v1.0 register | Deprecated; retire after v1.2 |
LC envelope 50 segments V3 IDs |
47 segments / 34.59 MWp v1.0 register | Deprecated; retire after v1.2 |
F.6.4 Sunset timelines¶
- Deprecation issued: with the version that introduces the replacement (v1.1.0 in most cases)
- Sunset period: one MINOR version cycle (typically 6–12 months)
- Retired: deprecation warning becomes a hard error; legacy artefacts updated to use new canonical
F.7 Document storage and Git¶
F.7.1 Google Drive canonical¶
methodology-package/ (ID 1NgoWojh63BXcbGgB7sIdfW79b5ail4p3) is the canonical location for all methodology documents (markdown source + Google Doc companion + annexes + retraction notices).
F.7.2 Git repository (AUDIT-033 closure)¶
Per AUDIT-033, the methodology is also Git-versioned. Repository structure:
nc-methodology/ # private GitHub or self-hosted
├── README.md
├── CHANGELOG.md
├── parts/
│ ├── A_framing.md
│ ├── B_pipeline.md
│ ├── C_typologies.md
│ ├── D_crosscutting.md
│ ├── E_runbook.md
│ └── F_governance.md
├── annexes/
│ ├── G_per_tenant_credit.md
│ ├── H_lc_cost_drivers.md
│ ├── I_pytest_suite.md
│ └── J_audit_register.md
├── tests/
│ ├── conftest.py
│ ├── test_replication.py
│ ├── test_cross_estate.py
│ ├── test_audit_findings.py
│ ├── test_governance.py
│ └── fixtures/
└── _drafts/ # working drafts pre-merge
Each version lock is a Git tag (e.g., v1.0, v1.1.0, v1.1.1).
F.7.3 Naming conventions¶
- Parts:
NC-METH-001_v{X.Y.Z}_Part_{LETTER}_{Name}.md(e.g.,NC-METH-001_v1.1.0_Part_F_Governance.md) - Annexes:
NC-METH-001_v{X.Y.Z}_Annex_{LETTER}_{Name}.md(e.g.,NC-METH-001_v1.1.0_Annex_H_LC_Cost_Drivers.md) - Google Doc companions: same title without
.mdbut with(Google Doc)suffix - Drafts:
_drafts/prefix or branch in Git
F.7.4 Distribution¶
- Markdown source: canonical truth in Git + mirrored to Drive
- Google Doc companion: auto-generated from markdown for in-Drive review (manual upload current practice; automation pending)
- PDF snapshot: generated at each MINOR/MAJOR version lock for distribution; archived in
methodology-package/_pdf_archive/
F.7.5 Methodology-package 2 retired¶
The methodology-package 2 folder (created during an earlier Drive sync mishap) is deprecated per F.6.3 and retired after audit-trail confirmation.
F.8 v1.1.0 lock gating events¶
NC-METH-001 v1.1.0 is currently in-progress. The version is locked when all of the following close:
F.8.1 Work-package closures (per R3 close plan)¶
| Work package | Owner | Output | Closes |
|---|---|---|---|
| WP1: Bankable PV Yield Study | Steven + commissioned vendor | Yield convention reconciliation (1,380 vs 1,485) + Solcast/PVGIS/Solargis cross-check | AUDIT-001, AUDIT-017 |
| WP2: LC-specific cost driver engineering review | Steven + engineering firm | Per-typology canonical CAPEX validated against LC v1.0; T1 $412 priority engineering review | AUDIT-040, AUDIT-002 |
| WP3: Financial model methodology alignment | Jin Yong + Steven | Model parameter alignment with methodology (5.75% debt; per-typology yield; per-typology O&M) | AUDIT-014, AUDIT-016, AUDIT-041 |
| WP4: Per-tenant credit framework | Benedikt + Jin Yong | Annex G (per-tenant credit grading + concentration treatment) | AUDIT-027 |
| WP5: KTB legal alignment | Marc + Baker McKenzie | KTB IE pre-engagement; ERPA structures validated | (closes residual governance items) |
F.8.2 Annex closures¶
| Annex | Status |
|---|---|
| Annex G Per-tenant credit framework | Pending WP4 |
| Annex H LC-specific cost driver documentation | Pending WP2 + WP4 — gating event for v1.1.0 |
| Annex I pytest acceptance test suite specification | Pending Annex H + WP3 |
| Annex J Audit register v0.3 → v1.0 closure status | Pending WP1–WP5 closures |
F.8.3 v1.1.0 lock criteria¶
All of the following must be true:
- ✅ Parts A–F written (this document family)
- ⏳ Annex G complete and reviewed
- ⏳ Annex H complete and reviewed (gating event)
- ⏳ Annex I complete and pytest suite operational
- ⏳ Annex J reflects all R3 register items as either closed or explicitly deferred to v1.2
- ⏳ Pytest test suite passes all replication + cross-estate ranking + high-materiality + governance tests
- ⏳ Change-log entry per F.1.3 drafted
- ⏳ M. Forni + S. Rubinyi joint approval per F.1.4
- ⏳ Git tag
v1.1.0applied - ⏳ PDF snapshot archived
- ⏳ IC and Fund I LPs notified
F.8.4 Expected v1.1.0 lock timeline¶
Per R3 close plan (5 WPs over 10 weeks, $85–115K all-in): - Weeks 1–4: WP1 + WP2 procurement - Weeks 5–8: WP3 financial model alignment; WP4 per-tenant credit; WP5 KTB legal - Weeks 9–10: Annex H + I + J completion; test suite operational; lock - Target lock date: 22 July 2026 (10 weeks from 12 May)
F.8.5 What happens if v1.1.0 doesn't lock on schedule¶
If WPs slip or Annex H requires additional engineering review: - v1.1.0-revB issued with partial closures (interim canonical) - v1.1.0 lock deferred until gating events close - IC and Fund I LPs notified of revised timeline
F.9 Acknowledged Part F gaps¶
- CI/CD pipeline for pytest suite — Part F specifies pytest as the test framework but assumes local execution; CI pipeline (GitHub Actions or equivalent) is v1.2 deliverable
- Distribution automation — markdown → Google Doc auto-generation not yet built; current practice is manual upload
- Per-estate methodology variants — methodology assumes single canonical applies to all 13 estates; estate-specific deviations (e.g., land-lease T1 invalid) are documented in Part E but not formalised as estate-typed methodology variants
- External reviewer integration — KTB IE and other external reviewers should be able to consume the methodology in a standard format; export protocols not yet documented
- Fund II methodology fork — when Fund II (VN/IDN/BD) launches 2027–28, methodology forks for international application; fork governance not yet documented
- Legal / IP treatment — methodology document contains commercially sensitive information; IP and confidentiality protocols not yet formalised beyond NDA defaults
These gaps are deferred to v1.2 unless escalated.
F.10 Closing¶
Part F closes the v1.1.0 methodology document family at the structural level. The actual v1.1.0 lock awaits: - WP1 (yield), WP2 (cost drivers), WP3 (financial model alignment), WP4 (per-tenant credit), WP5 (KTB legal) - Annex G, H, I, J - Test suite operational
Once these close, NC-METH-001 v1.1.0 is the canonical methodology for the IEAT Solar Investment Program. It supersedes v1.0 baseline (9 May 2026) and all retired or deprecated artefacts.
Subsequent versions (v1.1.1 PATCH, v1.2.0 MINOR, v2.0.0 MAJOR) follow Part F governance.
The methodology is now complete in its structural form: six Parts (A–F) + four annexes-in-progress (G/H/I/J) + two deferred annexes (K/L for v1.2). Total document length at v1.1.0 structural completion: ~30K words across 10 documents.
F.11 References¶
- NC-IC-LC-001 IC Paper v1.1 (28 April 2026)
- NC-FM-LC-001 LC Financial Model v1.0
- NC-IS-LC-001 LC Investment Segment Register v1.0
- NC-WP-LC-001 Phase 0 Work Plan v1.0
- NC-PR-LC-001 Procurement SOWs v1.0
- NC-MN-001-R3_audit_v0_3 — live audit register; v0.3 → v1.0 closure in Annex J
- NC-MN-001-R3_v1_1_close.md — work plan for v1.1.0 closures
- NC-MN-001-CLOSEOUT_MEMO.md — audit cycle close-out
- Memory edits 1–30 (per
memory_user_edits view12 May 2026) - NC-METH-001 v1.1.0 Part A — framing (semver framework)
- NC-METH-001 v1.1.0 Part B — pipeline
- NC-METH-001 v1.1.0-revA Part C — typologies (corrected)
- NC-METH-001 v1.1.0 Part D — cross-cutting modules
- NC-METH-001 v1.1.0 Part E — runbook
End of Part F v1.1.0.
End of NC-METH-001 v1.1.0 structural document family (Parts A–F).