User Manual Coverage Map

Purpose

This map tracks which high-value knowledge areas from the HAPI User Manual have been converted into Obsidian notes.

Coverage Summary

Manual AreaCoverage StatusNotes
HAPI system overviewCovered in Phase 1HAPI_System_Overview
Point Code Processing LogicCovered in Phase 1Point_Code, Numeric_Suffix, Clustering_Number, Rectangle_Fitting_Rules
Typical Plan Drafting WorkflowCovered in Phase 2ATypical_Plan_Drafting_Workflow
Series A script summariesCovered in Phase 2ASeries_A_Data_Exchange and A1a-A4 notes
Series B script summariesCovered in Phase 2ASeries_B_Drafting_Aids and B1-B3 notes
Series C script summariesCovered in Phase 2ASeries_C_Plan_Production and C1-C2 notes
Style Code Processing LogicCovered in Phase 1Style_Code, Style_Code_Input_Mechanisms
Typical ECM Modelling WorkflowCovered in Phase 2ATypical_ECM_Modelling_Workflow
Series E script summariesCovered in Phase 2ASeries_E_ECM_Modelling and E1-E4 notes
ECM-ready CSV appendixCovered in Phase 2AECM_Ready_CSV_File_Format
Point data file formatsCovered in Phase 2APoint_Data_File_Formats, File_Format_CSV, File_Format_PT2, File_Format_DTA, File_Format_XYZ
Changelog / Release contextPartly coveredSummarised in gap register; may become a dedicated note later.
Full Feature Code Reference TableIntentionally not reproducedFeatureCatalogue.json is the single source of truth.

High-Importance Knowledge Completion

The high-importance missing knowledge identified after Phase 1 has now been addressed in Phase 2A:

  • script-specific summaries;
  • typical plan drafting workflow;
  • typical ECM modelling workflow;
  • script input/output details;
  • ECM-ready CSV appendix;
  • point data file format rules.

Feature Code Reference Policy

The manual contains a Feature Code Reference Table, but it should not be manually reproduced in Obsidian. The current source of truth for feature-related information is FeatureCatalogue.json. A future generated reference may be created from the JSON if needed.

Built with LogoFlowershow