2 Commits

Include renames

Author	SHA1	Message	Date
jared	93300ae0c1	feat: three-concept expenditure model classified by crosswalk membership (#11) ... Rewrites expenditure/revenue classification off item-code first-letter prefixes and onto summary_categories membership (F-018: prefix Y spans revenue, expenditure, and balance codes), and exposes expenditure_concept = c("primary", "direct", "total") with primary as the new default: primary = operations + capital + assistance direct = primary + interest + insurance_benefits (Census Direct) total = direct + intergovernmental (M/L/Q via ig views) - inst/sql: flow views (20-25) select by crosswalk membership; summary_categories moves to 11- so it registers before them (DuckDB binds view sources eagerly). The IG leg gains Q11/Q12/Q18 state school-system payments (F-017). - R: one subtype scope per verb call drives the verb SQL, the harmonization exclusion count, and the complete = TRUE grid; flow_prefixes survives only to scope recipe suggestions. cog_geographic_rollup/cog_peer_compare accept primary|direct, still refuse total, and now actually pass the concept through. - Balance codes can never reach a spending or revenue result (uscogdata#25), asserted at both view and verb level. - Deletes the #11 skip; per the 2026-07-30 owner ruling the F-018 Y01 proof is asserted against the crosswalk, not the default cog_revenue() call (which stays General Revenue pending #12). Suite: 696 pass / 0 fail / 1 skip (#12, expected). Closes #11	2026-07-30 16:56:50 -04:00
jared	7818cd2b1a	feat: basis= harmonized/raw with v4/v5 dual-accept ... Adds schema_version 5 support alongside the existing v4 corpus: .validate_schema() now accepts a supported set (4, 5) instead of a single expected version, and cog_spending()/cog_revenue() gain basis = c("harmonized", "raw"). Harmonized basis routes to new spending_annotated_harmonized / revenue_annotated_harmonized views built on spending_long_harmonized / revenue_long_harmonized (REPLACE(harmonized_code AS item_code), excluding aggregate and NA-harmonized rows); raw basis is byte-identical to the pre-Phase-R2 behavior. On a v4 corpus, an unspecified basis silently resolves to "raw" with a provenance note; an explicit basis = "harmonized" aborts with an actionable message. Provenance gains basis, basis_note, and a harmonization block (applied/na_rows_excluded/na_amount_excluded). The five new schema-v5-only SQL views (harmonized long/annotated views, harmonization_map, harmonization_recipes, series_breaks_pq) are registered conditionally on manifest$schema_version >= 5, since DuckDB's read_parquet() errors eagerly at CREATE VIEW time when the backing file doesn't exist on a v4 corpus. Fixture corpus regenerated to schema_version 5 / years 2011, 2012, 2019, 2020 (2011->2012 spans the wide-aggregate -> modern-leaf format boundary needed for the harmonization/recipe work), with the harmonization_map / harmonization_recipes / series_breaks parquet tables bundled alongside the existing metadata registries.	2026-07-18 23:19:17 -04:00