MarketIR Preview
Deterministic marketing IR — claims, evidence, and channel messaging.
zip-meta-map
Make repos and ZIPs self-describing for LLMs with CI-grade diffs.
Value Propositions
- Deterministic index: same repo produces the same output, every time
- Token-budgeted LLM plans: structured context that fits in context windows
- CI gating with diff --exit-code: fail builds when metadata drifts
- JSON Schema-validated output with a passing test suite backing correctness
Anti-Claims
- Does not replace code search or embeddings — it complements them with structural metadata.
- Does not perform runtime vulnerability scanning — heuristic flagging is advisory, not CVE-grade.
- Does not require or assume any specific LLM provider — output is plain JSON consumable by any tool.
Audiences
CI/CD Maintainers
Engineers who own CI pipelines and care about build reproducibility, PR gating, and pipeline trust.
- No confidence that repo metadata is fresh or accurate after merges
- PR reviews lack machine-readable context about what changed structurally
- Build artifacts drift silently — same repo, different metadata depending on when you run
- Hard to enforce metadata quality gates without custom scripting
LLM Toolchain Developers
Developers building AI agents and LLM-powered tools that need structured repo context under token budgets.
- LLM agents waste tokens on irrelevant files when given raw directory listings
- No standard format for repo structure that LLMs can consume efficiently
- Token budget overruns when context windows are limited
- Manual curation of repo maps doesn't scale across projects
Claims
claim.zip-meta-map.deterministic-output Given the same repository state, zip-meta-map produces byte-identical index output.
Awaiting upstream zip-meta-map repo public release; downgraded from proven 2026-05-15. Backing evidence (test_report_deterministic, test_diff identical-indices, deterministic chunker tests) lives in the upstream repo and will be re-linked once public.
claim.zip-meta-map.test-suite Every release ships with a passing test suite that exercises CLI, schema, and diff behavior.
Awaiting upstream zip-meta-map repo public release; downgraded from proven 2026-05-15. Restated as a stable property (no hardcoded count) per F-CONTRACT-007. Renamed from claim.zip-meta-map.246-tests in v0.10 slice 2; old ID retained in aliases[] for downstream consumer resolution. Backing evidence is the upstream CI run history.
claim.zip-meta-map.ci-gating zip-meta-map diff --exit-code returns non-zero when metadata drifts, suitable for CI gating.
Awaiting upstream zip-meta-map repo public release; downgraded from proven 2026-05-15. Backing evidence is the upstream CI workflow definition (uses diff --exit-code for gating).
claim.zip-meta-map.token-budgets LLM plans respect configurable token budgets, producing structured context that fits within specified limits.
Algorithmic claim; awaiting falsifiable test-report evidence (token-budget property test). Downgraded from proven 2026-05-15.
claim.zip-meta-map.schema-validated All output conforms to a published JSON Schema, validated in CI on every commit.
Awaiting upstream zip-meta-map repo public release; downgraded from proven 2026-05-15. Backing evidence is the upstream CI test suite that runs schema validation on every commit.
claim.zip-meta-map.sub-second-builds Typical repo builds complete in under one second on commodity hardware.
Anecdotally true but not yet benchmarked with reproducible methodology.
Messages
Campaigns
zip-meta-map Launch
Phase 1: Soft launch
Get the tool page and README polished before any external promotion.
Phase 2: Community launch
HN Show + X post. Time for weekday morning US-East.
Phase 3: Professional outreach
LinkedIn post targeting engineering leaders and DevOps.