npm - @pikaa-ai/pikaa - Versions diffs - 0.3.1 → 0.3.4 - Mend

@pikaa-ai/pikaa 0.3.1 → 0.3.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (1870) hide show

package/skills/market-research-reports/references/official_data_sources.md DELETED Viewed

@@ -1,196 +0,0 @@
-# Official Data and Filing Sources
-Verified against first-party guidance on 2026-07-23. API rules can change:
-recheck the linked terms and limits before automated or high-volume use. The
-bundled scripts do not call these services and do not require API keys.
-## Routing by claim
-Start with the original authority most fit for the claim:
-- company financials and risk disclosures: the jurisdiction's official filing
-  system, then the filed document;
-- establishment, employment, prices, production, trade, population, and GDP:
-  the responsible national statistical office or central bank;
-- rules, approvals, enforcement, licenses, and consultations: the responsible
-  regulator or official legal gazette;
-- cross-country indicators: the original national source when comparability is
-  not required; otherwise an international harmonized dataset with metadata;
-- classifications: the current official NAICS, NACE, ISIC, product, trade, or
-  sector taxonomy and its correspondence tables.
-Do not treat an aggregator as an independent corroborating source when it
-reproduces the same underlying series.
-## United States
-### SEC EDGAR and company filings
-- [SEC Developer Resources](https://www.sec.gov/about/developer-resources)
-  documents company submissions and extracted XBRL data APIs.
-- [Accessing EDGAR Data](https://www.sec.gov/search-filings/edgar-search-assistance/accessing-edgar-data)
-  requires a declared user agent and states a current maximum of 10 requests per
-  second across the user's machines. Download only what is needed.
-- EDGAR filings can be corrected or removed after acceptance. Record accession
-  number, form, filing date, reporting period, amendment status, exact table or
-  XBRL fact, units, and retrieval date.
-- Consolidated company revenue is not automatically market revenue. Remove
-  out-of-scope products/geographies and avoid summing parent/subsidiary or
-  channel/end-customer values twice.
-### U.S. Census Bureau
-- The [Census Data API User Guide](https://www.census.gov/data/developers/guidance/api-user-guide.html)
-  links data to a geographic boundary and a dataset vintage.
-- As revised 2026-05-14, the
-  [query-limits page](https://www.census.gov/data/developers/guidance/api-user-guide.Query_Limits.html)
-  permits up to 50 variables per query and requires a key for all data queries.
-  The [key page](https://www.census.gov/data/developers/guidance/api-user-guide.API_Key.html)
-  describes free registration. Never place a key in a report, source ledger, or
-  bundled script.
-- Use program-specific methodology, margins of error, universe, geography, and
-  vintage. ACS estimates, Population Estimates, and decennial counts are not
-  interchangeable.
-- The [2022 Economic Census methodology](https://www.census.gov/programs-surveys/economic-census/year/2022/technical-documentation/methodology.html)
-  defines the target population, sampling frame, exclusions, administrative
-  data, imputation, disclosure avoidance, and product collection.
-- The [NAICS site](https://www.census.gov/naics) identifies 2022 NAICS as the
-  current published structure while a 2027 revision process is underway. Store
-  the version used.
-### Bureau of Labor Statistics
-The [BLS API FAQ](https://www.bls.gov/developers/api_faqs.htm), last modified
-2023-08-30, documents:
-- registered v2: 500 queries/day, 50 series/query, 20 years/query;
-- unregistered v1: 25 queries/day, 25 series/query, 10 years/query;
-- both: 50 requests per 10 seconds;
-- v2 registration renewal at least annually;
-- v1 returns observations and footnotes without descriptive metadata.
-Record series ID, survey/program, seasonal adjustment, units, frequency,
-footnotes, publication date, and revision status. Consult the program's
-methodology and release calendar rather than relying on the API response alone.
-### Bureau of Economic Analysis
-The [BEA API User Guide](https://apps.bea.gov/api/_pdf/bea_web_service_api_user_guide.pdf),
-dated 2026-04-20, requires a registered UserID and documents three rolling
-per-minute limits:
-- 100 requests;
-- 100 MB retrieved;
-- 30 errors.
-BEA returns HTTP 429 and a `Retry-After` header when throttled. The guide warns
-that limits may change. Query metadata methods before data, restrict years and
-dimensions, and avoid broad `ALL` requests. Record current versus chained
-dollars, reference year, table/line code, frequency, seasonality, and release
-vintage. Chained-dollar components may not be additive; use published
-contributions or current-dollar shares where appropriate.
-### Federal Reserve and FRED/ALFRED
-- [FRED API documentation](https://fred.stlouisfed.org/docs/api/fred/) describes
-  v2 bulk release history and v1 series-level FRED/ALFRED access.
-- A registered key is required under the
-  [FRED API Terms](https://fred.stlouisfed.org/docs/api/terms_of_use.html).
-  The reviewed terms do not state one fixed numerical request ceiling; they
-  reserve the right to impose or change limits.
-- The terms warn that third parties may own series and impose additional
-  restrictions. Follow the original producer's rights and attribution.
-- FRED normally presents latest values; ALFRED preserves real-time vintages.
-  Record source, release, series ID, frequency, units, seasonal adjustment,
-  notes, and vintage dates.
-## International and harmonized sources
-### World Bank
-The [Indicators API documentation](https://datahelpdesk.worldbank.org/knowledgebase/articles/889392-about-the-indicators-api-documentation)
-states that v2 is current, v1 is discontinued, and API authentication is not
-required. Preserve indicator code, database/source, source note, source
-organization, unit, income/region classification vintage, and retrieval date.
-The [WDI catalog](https://datacatalog.worldbank.org/search/dataset/0037712/world-development-indicators)
-publishes metadata and revision-history resources. A World Bank indicator may
-originate with a national agency or another international organization; retain
-that lineage.
-### International Monetary Fund
-The [IMF Data API page](https://data.imf.org/en/Resource-Pages/IMF-API) states
-that IMF data are available through SDMX 2.1 and SDMX 3.0 APIs. Use the
-dataset's data structure, codelists, unit, scale, frequency, observation status,
-and methodological metadata. Do not assume similarly named indicators across
-IMF datasets have identical definitions.
-### OECD
-The [OECD Data Explorer API guide](https://www.oecd.org/en/data/insights/data-explainers/2024/09/api.html),
-published 2025-04-30, describes the SDMX API, free access subject to OECD terms,
-and rate limiting without publishing one universal numerical ceiling on that
-page. It warns that omitting a dataflow version selects the latest version and
-that later structures may not be backward compatible. Store agency, dataset,
-dataflow version, dimensions, codes, attributes, and query.
-### Eurostat
-The [Eurostat API introduction](https://ec.europa.eu/eurostat/web/user-guides/data-browser/api-data-access/api-introduction)
-documents Statistics, SDMX 2.1, SDMX 3.0, catalogue, and asynchronous services.
-It states that datasets are updated twice daily when changes are available and
-that the database contains only the latest version, without past-version
-documentation. Preserve the retrieved file and update timestamp when a
-reproducible vintage matters.
-The [ESS quality and metadata handbook](https://ec.europa.eu/eurostat/web/products-manuals-and-guidelines/-/ks-gq-21-021)
-is a standard for reporting source, process, quality, and metadata. Record flags,
-breaks, seasonal adjustment, units, NUTS/geography version, and dataset code.
-### Other national statistical agencies
-Use the relevant country's official agency before secondary compilations.
-Examples of current first-party interfaces:
-- [Statistics Canada Web Data Service](https://www.statcan.gc.ca/en/developers/wds/user-guide)
-  provides data and metadata. Guide revision 1.6 (2025-01-24) documents a
-  50-request/second server limit and 25-request/second individual IP limit, and
-  possible HTTP 409 responses during update windows.
-- The [UK ONS Developer Hub](https://developer.ons.gov.uk/) describes an open,
-  no-key beta API. It warns that breaking changes can occur; store dataset,
-  edition, and version because new versions reflect corrections, revisions, or
-  new data.
-For any country, confirm:
-1. the official statistics producer and legal mandate;
-2. release calendar, methodology, quality statement, and revision policy;
-3. classification and geography versions;
-4. API/download terms and current operational limits;
-5. whether the dataset is official, experimental, modeled, or an administrative
-   extract.
-## Industry and product classifications
-- [NAICS](https://www.census.gov/naics) classifies establishments by primary
-  economic activity; it is not itself a product-market definition.
-- [NACE Rev. 2.1](https://ec.europa.eu/eurostat/web/products-eurostat-news/w/wdn-20250624-1)
-  began feeding European statistics from 2025. Use the 2025 manual and
-  correspondence tables when comparing Rev. 2 and Rev. 2.1.
-- Product classifications (NAPCS, CPA, PRODCOM, CPC, HS/CN) may fit market
-  outputs better than an establishment-based industry code.
-- A concordance can be one-to-many or many-to-many. Never apply it as a
-  lossless conversion without weights and uncertainty.
-## API handling rules
-- Use APIs only during research, with user-approved network access.
-- Keep credentials outside reports and scripts; never commit keys.
-- Respect official terms, user-agent requirements, rate limits, retries, and
-  bulk-download guidance.
-- Cache lawful downloads, record the exact query and retrieval time, and avoid
-  repeatedly requesting unchanged data.
-- Validate response status, metadata, units, flags, suppression, and missing
-  values before analysis.
-- Treat current limits in this file as a dated snapshot, not a permanent
-  entitlement.

package/skills/market-research-reports/references/report_structure_guide.md DELETED Viewed

@@ -1,283 +0,0 @@
-# Market Research Report Structure
-Match the report to the decision and available evidence. There is no required
-page count, chapter count, figure count, or output format. Omit irrelevant
-modules and expand methods/limitations when uncertainty is high.
-## Front matter
-### Title and scope
-Include:
-- market and geography;
-- historical and forecast periods;
-- retrieval cutoff;
-- report version and classification;
-- sponsor, author, and material conflicts;
-- explicit statement that the report is not investment, legal, or financial
-  advice.
-Do not use logos, layouts, or wording that imply affiliation with another firm.
-### Executive synopsis
-Write last. It should stand alone and contain:
-1. decision context;
-2. formal market boundary in one sentence;
-3. highest-confidence findings with claim IDs;
-4. top-down and bottom-up scenario range;
-5. forecast scenario range and principal sensitivity;
-6. material conflicts and limitations;
-7. implications or options clearly labeled as judgment.
-Never introduce a metric in the synopsis that is absent from the evidence and
-claims ledgers.
-## 1. Scope and definitions
-Define:
-- product/service inclusion and exclusion;
-- customer, payer, user, and transaction;
-- value-chain level;
-- geography, imports/exports, and channels;
-- time basis and as-of date;
-- measure, unit, and denominator;
-- stock/flow and gross/net treatment;
-- currency, base year, and nominal/real basis;
-- industry and product classifications with versions;
-- adjacent markets that are excluded.
-Explain alternate plausible definitions and why one was selected. An industry
-classification is not automatically a product market or an antitrust market.
-## 2. Evidence and methods
-Describe:
-- source hierarchy and search cutoff;
-- original data producers and aggregator lineage;
-- exact claim-source mapping;
-- archived snapshots and revision handling;
-- extraction, cleaning, joins, conversions, and calculations;
-- source conflicts and reconciliation rules;
-- confidence labels;
-- primary-research methods and privacy controls;
-- missing evidence and analysis deviations.
-Summarize the source ledger by source type and revision status. Do not inflate
-source count by counting mirrors or derivative articles as independent.
-## 3. Market size
-### Top-down
-Show:
-- control total and definition;
-- disjoint components and coverage keys;
-- in-scope fractions;
-- channel/tax/trade adjustments;
-- source IDs and limitations;
-- resulting TAM scenarios.
-### Bottom-up
-Show:
-- population or installed base;
-- customer segments;
-- annual units or transactions;
-- price/spend assumptions;
-- addressable fractions;
-- source and assumption IDs;
-- resulting TAM scenarios.
-### SAM and SOM
-For each scenario, state:
-- serviceability filters;
-- capture-share assumptions;
-- time horizon;
-- capacity, channel, sales-cycle, retention, and competition constraints;
-- source evidence and analyst assumptions.
-Present TAM/SAM/SOM as conditional scenarios. Do not select one estimate merely
-because it is the midpoint.
-### Reconciliation and sensitivity
-Report:
-- absolute and percentage gap between methods;
-- definition, denominator, and coverage-key comparison;
-- corrections for double counting;
-- remaining unexplained difference;
-- sensitivity to major counts, price, penetration, serviceability, and capture;
-- switching values that change a decision.
-## 4. Demand and customer evidence
-Separate:
-- official/administrative or transactional evidence;
-- published survey evidence;
-- original survey evidence;
-- interview/focus-group themes;
-- analyst interpretation.
-For survey claims, include population, frame, sample method, mode, dates,
-unweighted sample, weighting, response/participation, wording, precision, and
-limitations. For interviews, include recruitment, consent, roles, mode, dates,
-coding, divergent views, and limits to generalization.
-## 5. Market dynamics
-For each driver or inhibitor:
-- state the mechanism;
-- identify observed evidence versus assumption;
-- quantify only with a defensible calculation;
-- define time horizon and leading indicators;
-- include disconfirming evidence;
-- state how it changes a scenario input.
-Frameworks such as PESTLE or SWOT may organize questions but are not evidence.
-Use them only when useful, and do not force a fixed number of factors or scores.
-## 6. Competitive landscape
-### Scope
-Define the product and geographic basis from the customer perspective. Consider
-substitutability, non-price dimensions, channels, imports, digital/multi-sided
-features, innovation, and dynamic change where relevant.
-### Competitor set
-State inclusion rules. Distinguish:
-- current direct competitors;
-- adjacent/substitute providers;
-- potential entrants;
-- channel partners or suppliers;
-- unknown/private participants.
-### Feature and positioning evidence
-Use the validated matrix with product edition, geography, date, status, and
-source IDs. Publish scoring rules for any positioning map. Use `unknown` when
-evidence is absent.
-### Shares and concentration
-State numerator and denominator, metric, period, coverage, residual share, and
-alternate definitions. Treat HHI/CRn as descriptive screens. Do not make legal
-antitrust conclusions.
-## 7. Forecast scenarios
-### Historical basis
-Show series IDs, units, frequency, seasonal adjustment, revisions, taxonomy
-breaks, transformations, and vintage.
-### Scenario design
-For each named scenario, document:
-- annual rate path or driver equations;
-- demand, price, supply, regulation, competition, and capacity assumptions;
-- evidence and assumption IDs;
-- constraints and internal consistency;
-- conditions that would make the scenario obsolete.
-Do not assign probabilities without a defensible probabilistic model. Do not
-call scenario bounds confidence or prediction intervals.
-### Sensitivity
-Report endpoints under stated input shifts, rank influential assumptions, and
-identify decision thresholds. If interactions matter, add coherent combined
-scenarios rather than relying only on one-way sensitivity.
-## 8. Regulation and policy
-Use primary regulator and legal sources. Record:
-- jurisdiction and authority;
-- instrument or docket identifier;
-- publication, adoption, and effective dates;
-- enacted/proposed/stayed/repealed status;
-- affected products and entities;
-- evidence-backed market mechanism;
-- uncertainty and need for legal review.
-Do not present a policy proposal as effective law or compliance interpretation
-as legal advice.
-## 9. Risks, implications, and options
-Separate:
-- observed risk indicator;
-- likelihood judgment;
-- impact mechanism;
-- exposure and time horizon;
-- early-warning measure;
-- mitigation or option;
-- residual uncertainty.
-Tie recommendations to explicit objectives and findings. Include dependencies,
-trade-offs, owner, timing, and evidence that would trigger revision. A
-recommendation is judgment, not a sourced fact.
-## 10. Limitations
-Consolidate:
-- data gaps and source conflicts;
-- paid or inaccessible evidence not verified;
-- classification and scope mismatch;
-- currency/base-year and conversion limits;
-- stock/flow or denominator uncertainty;
-- revisions and historical breaks;
-- imputation, suppression, survey, and interview limitations;
-- competitor evidence gaps;
-- forecast/model uncertainty;
-- sponsor and analyst conflicts.
-## Appendices
-Include as needed:
-- source/evidence ledger;
-- claims ledger;
-- calculation and assumption register;
-- unit/currency/base-year conversion table;
-- market-sizing inputs and outputs;
-- forecast and sensitivity inputs and outputs;
-- competitor-feature matrix;
-- survey instrument and methodology disclosure;
-- interview guide and de-identified coding framework;
-- revision log;
-- machine-readable local files.
-## Release gate
-- Scope and denominator are explicit and consistent.
-- Every factual or quantitative claim maps to source IDs.
-- Calculations map to inputs and assumptions.
-- Publication/retrieval dates and revisions are recorded.
-- Monetary values identify currency, base year, and price basis.
-- Stock/flow, units, taxonomy, and denominator are explicit.
-- Top-down/bottom-up methods are reconciled without double counting.
-- TAM/SAM/SOM and forecasts are conditional scenarios with sensitivity.
-- Survey and interview evidence carries full method and privacy disclosures.
-- Competitor evidence is lawful, dated, and does not infer `no` from `unknown`.
-- Conflicts and limitations remain visible.
-- No unsupported paid-market figures, fabricated citations, PII, trade secrets,
-  deceptive collection, brand impersonation, or investment-advice framing.

package/skills/market-research-reports/references/sources.md DELETED Viewed

@@ -1,73 +0,0 @@
-# Dated Source Ledger
-Research cutoff and retrieval date: **2026-07-23**.
-Sources were located and checked with focused `parallel-cli search` queries and
-canonical-page `parallel-cli extract` calls. Only first-party or primary
-methodological sources are listed below. Dates are publication, document, or
-last-revised dates stated by the source; `not stated` is used rather than
-guessing.
-## Corporate filings and U.S. official data
-| ID | Authority | Source and date | Use |
-|---|---|---|---|
-| SRC-SEC-ACCESS | U.S. SEC | [Accessing EDGAR Data](https://www.sec.gov/search-filings/edgar-search-assistance/accessing-edgar-data), published 2021-03-23; updated 2024-06-26 | EDGAR history, corrections, declared user agent, 10 requests/second fair-access limit |
-| SRC-SEC-DEV | U.S. SEC | [Developer Resources](https://www.sec.gov/about/developer-resources), updated 2025-03-10 | Submissions and XBRL APIs; fair-access overview |
-| SRC-CENSUS-API | U.S. Census Bureau | [Census Data API User Guide](https://www.census.gov/data/developers/guidance/api-user-guide.html), dated 2026-05-12; revised 2026-05-14 | Geography/vintage concepts and API navigation |
-| SRC-CENSUS-LIMIT | U.S. Census Bureau | [Query Limits](https://www.census.gov/data/developers/guidance/api-user-guide.Query_Limits.html), revised 2026-05-14 | 50 variables/query; key required for data queries |
-| SRC-CENSUS-KEY | U.S. Census Bureau | [API Key](https://www.census.gov/data/developers/guidance/api-user-guide.API_Key.html), revised 2026-05-14 | Current free key-registration guidance |
-| SRC-EC-METHOD | U.S. Census Bureau | [2022 Economic Census Methodology](https://www.census.gov/programs-surveys/economic-census/year/2022/technical-documentation/methodology.html), updated 2026-04-10 | Population, frame, NAICS scope, collection, administrative data, imputation, disclosure avoidance |
-| SRC-NAICS | U.S. Census Bureau | [NAICS](https://www.census.gov/naics), revised 2026-07-23 | Current 2022 structure and 2027 revision process |
-| SRC-BLS-API | U.S. Bureau of Labor Statistics | [Public Data API FAQ](https://www.bls.gov/developers/api_faqs.htm), modified 2023-08-30 | Registration, daily/rate/series/year limits, metadata behavior |
-| SRC-BEA-API | U.S. Bureau of Economic Analysis | [BEA API User Guide](https://apps.bea.gov/api/_pdf/bea_web_service_api_user_guide.pdf), 2026-04-20 | UserID, metadata calls, 100 requests/minute, 100 MB/minute, 30 errors/minute, HTTP 429/retry |
-| SRC-BEA-CHAIN | U.S. Bureau of Economic Analysis | [Chained-Dollar Indexes: Issues and Tips](https://www.bea.gov/resources/methodologies/chained-dollar-indexes), published 2003-11; page modified 2018-05-30 | Real/current measures, chain weighting, non-additivity |
-| SRC-FRED-API | Federal Reserve Bank of St. Louis | [FRED API](https://fred.stlouisfed.org/docs/api/fred/), date not stated | v1 series/ALFRED access; v2 bulk release history; metadata and vintage endpoints |
-| SRC-FRED-TERMS | Federal Reserve Bank of St. Louis | [FRED API Terms](https://fred.stlouisfed.org/docs/api/terms_of_use.html), date not stated | Key requirement, changeable limits, application notice, third-party rights |
-## International and national statistical systems
-| ID | Authority | Source and date | Use |
-|---|---|---|---|
-| SRC-WB-API | World Bank | [Indicators API Documentation](https://datahelpdesk.worldbank.org/knowledgebase/articles/889392-about-the-indicators-api-documentation), date not stated | v2 current; v1 discontinued; no API authentication; source metadata |
-| SRC-WB-WDI | World Bank | [World Development Indicators catalog](https://datacatalog.worldbank.org/search/dataset/0037712/world-development-indicators), updated 2026-07-22 | Metadata, classifications, and revision-history resources |
-| SRC-IMF-API | International Monetary Fund | [IMF Data APIs](https://data.imf.org/en/Resource-Pages/IMF-API), page dated 2026 | SDMX 2.1 and 3.0 access |
-| SRC-IMF-SDMX | International Monetary Fund | [IMF SDMX Central Web Services Guide](https://dsbb.imf.org/content/pdfs/IMFSDMXCentralWebServicesGuide.pdf), updated 2025-05 | Structures, codelists, schemas, and SDMX services |
-| SRC-OECD-API | OECD | [OECD data via API](https://www.oecd.org/en/data/insights/data-explainers/2024/09/api.html), 2025-04-30 | SDMX syntax, dataflow version warning, formats, terms, nonnumeric rate-limiting statement |
-| SRC-OECD-SUT | OECD | [Supply and Use Tables](https://www.oecd.org/en/data/datasets/supply-and-use-tables.html), date not stated | Product/industry supply-use framework and origin/use of goods and services |
-| SRC-EUROSTAT-API | Eurostat | [API Introduction](https://ec.europa.eu/eurostat/web/user-guides/data-browser/api-data-access/api-introduction), date not stated | Statistics/SDMX services, formats, twice-daily updates, latest-version-only caveat |
-| SRC-ESS-QUALITY | Eurostat | [ESS Handbook for Quality and Metadata Reports](https://ec.europa.eu/eurostat/web/products-manuals-and-guidelines/-/ks-gq-21-021), 2021-12-09 | Standardized quality and metadata reporting |
-| SRC-NACE | Eurostat | [NACE Rev. 2.1 manual announcement](https://ec.europa.eu/eurostat/web/products-eurostat-news/w/wdn-20250624-1), 2025-06-24 | Current NACE manual, principles, explanatory notes, correspondence tables |
-| SRC-STATCAN-WDS | Statistics Canada | [Web Data Service User Guide](https://www.statcan.gc.ca/en/developers/wds/user-guide), revision 1.6 dated 2025-01-24 | Data/metadata service, update window, 50 server and 25 per-IP requests/second |
-| SRC-ONS-API | UK Office for National Statistics | [ONS Developer Hub](https://developer.ons.gov.uk/), date not stated; beta | Open/no-key API; dataset/edition/version and breaking-change warning |
-## Market definition, uncertainty, and research methods
-| ID | Authority | Source and date | Use |
-|---|---|---|---|
-| SRC-US-MERGER | U.S. DOJ and FTC | [2023 Merger Guidelines](https://www.ftc.gov/system/files/ftc_gov/pdf/2023_merger_guidelines_final_12.18.2023.pdf), 2023-12-18 | Relevant markets, shares, HHI, evidence, dynamic and potential competition |
-| SRC-EU-MARKET | European Commission | [Market Definition Notice](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=OJ:C_202401645), 2024-02-22 | Product/geographic scope, non-price competition, digital/dynamic markets, alternate share metrics, evidence |
-| SRC-OMB-A4 | U.S. Office of Management and Budget | [Circular A-4](https://www.whitehouse.gov/wp-content/uploads/2023/11/CircularA-4.pdf), 2023-11-09 | Evidence quality, uncertainty, sensitivity, assumptions, transparent presentation |
-| SRC-GREENBOOK | UK HM Treasury | [The Green Book 2026](https://www.gov.uk/government/publications/the-green-book-appraisal-and-evaluation-in-central-government/the-green-book-2026), 2026-03-10 | Appraisal, options, uncertainty, evidence, and transparent assumptions |
-| SRC-AAPOR-CODE | American Association for Public Opinion Research | [Code of Professional Ethics and Practices](https://aapor.org/standards-and-ethics/), revised 2026-06 | Current participant, privacy, sponsor, public, integrity, and disclosure duties |
-| SRC-AAPOR-DISC | American Association for Public Opinion Research | [Disclosure Standards](https://aapor.org/standards-and-ethics/disclosure-standards/), code approved 2021-04; page published 2022-12-02 | Sponsor, instrument, population, sample, mode, dates, weighting, precision, limitations, privacy |
-| SRC-AAPOR-BEST | AAPOR | [Best Practices for Survey Research](https://aapor.org/standards-and-ethics/best-practices/), page published 2023-01-11 | Survey design, probability/non-probability samples, wording, weighting, reporting |
-| SRC-FCSM-NR | Federal Committee on Statistical Methodology | [Best Practices for Nonresponse Bias Reporting](https://statspolicy.gov/assets/fcsm/files/docs/FCSM%20NRBA%20Report%20062623.pdf), 2023-06 | Response-rate and subgroup nonresponse-bias reporting |
-| SRC-ICSP-QUALITY | Interagency Council on Statistical Policy | [Principles for Modernizing Production of Federal Statistics](https://statspolicy.gov/assets/fcsm/files/docs/Principles-2.pdf), 2018 | Quality, transparency, and limitations for statistical/non-statistical integrated data |
-| SRC-FORCE11 | FORCE11 | [Joint Declaration of Data Citation Principles](https://force11.org/group/joint-declaration-of-data-citation-principles-final), 2014; page date not stated | Importance, credit, evidence, unique identification, access, persistence, specificity |
-| SRC-ICO-MIN | UK Information Commissioner's Office | [Data minimisation](https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/data-protection-principles/a-guide-to-the-data-protection-principles/data-minimisation), updated 2025-09-09 | Collecting data adequate, relevant, and limited to purpose where UK GDPR applies |
-## Research query record
-Focused search/extract objectives covered:
-- SEC EDGAR, Census, BLS, BEA, FRED access, metadata, terms, and limits;
-- World Bank, IMF, OECD, Eurostat, Statistics Canada, and ONS APIs;
-- NAICS/NACE versions and classification correspondence;
-- supply-use/economic-census methods for sizing and double-count prevention;
-- U.S. and EU competition/market-definition guidance;
-- OMB and HM Treasury forecast uncertainty and sensitivity;
-- AAPOR/FCSM survey disclosure and nonresponse;
-- data citation, provenance, metadata quality, privacy, and ethical collection.
-No Parallel search JSON artifacts are included in the skill.