Internal Preview

MarketIR Preview

Deterministic marketing IR — claims, evidence, and channel messaging.

Branch main
Lock SHA256 210820f16a9728b7...
Fetched Feb 22, 2026, 3:53 PM
Files 7

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 246 tests 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.

Pain points:
  • 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.

Pain points:
  • 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

proven claim.zip-meta-map.deterministic-output

Given the same repository state, zip-meta-map produces byte-identical index output.

Evidence:
link ev.zip-meta-map.deterministic-test.v1
https://github.com/mcp-tool-shop-org/zip-meta-map/blob/main/tests/test_report.py
Generator: human Commit: 5be4b38 Contains test_report_deterministic() proving same index = identical output. Also test_diff.py:test_identical_indices_no_changes and test_chunker.py for deterministic chunking.
proven claim.zip-meta-map.246-tests

The test suite contains 246 passing tests covering CLI, schema validation, and diff behavior.

Evidence:
link ev.zip-meta-map.test-suite.v1
https://github.com/mcp-tool-shop-org/zip-meta-map/actions
Generator: github-actions-ci Commit: 5be4b38 246 passing tests as of v0.2.1. Link to CI runs; hash is zero because this is a live external resource.
proven claim.zip-meta-map.ci-gating

zip-meta-map diff --exit-code returns non-zero when metadata drifts, suitable for CI gating.

Evidence:
link ev.zip-meta-map.ci-step-summary.v1
https://github.com/mcp-tool-shop-org/zip-meta-map/blob/main/.github/workflows/ci.yml
Generator: github-actions-ci Commit: 5be4b38 CI workflow uses diff --exit-code for gating. Link to workflow definition; hash is zero because this is a live external resource.
proven claim.zip-meta-map.token-budgets

LLM plans respect configurable token budgets, producing structured context that fits within specified limits.

Evidence:
image ev.zip-meta-map.build-screenshot.v1
ev.zip-meta-map.build-screenshot.v1
Generator: scripts/gen-zmm-screenshot.mjs Commit: 2c3184d Generated from real zip-meta-map build index. Shows 73 files, 18 modules, 5 plans, 14 flagged, role distribution, LLM plan budgets.
proven claim.zip-meta-map.schema-validated

All output conforms to a published JSON Schema, validated in CI on every commit.

Evidence:
link ev.zip-meta-map.test-suite.v1
https://github.com/mcp-tool-shop-org/zip-meta-map/actions
Generator: github-actions-ci Commit: 5be4b38 246 passing tests as of v0.2.1. Link to CI runs; hash is zero because this is a live external resource.
aspirational 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

web pragmatic msg.zip-meta-map.web-blurb
zip-meta-map makes repos self-describing for LLMs. Deterministic builds, token-budgeted plans, and CI gating with 246 tests backing every claim.
max 280 chars
Claims: zip-meta-map.deterministic-outputzip-meta-map.token-budgetszip-meta-map.ci-gatingzip-meta-map.246-tests
readme technical msg.zip-meta-map.readme-snippet
Build a self-describing index of any repo or ZIP. JSON Schema-validated output, configurable LLM token budgets, and diff --exit-code for CI gating. 246 tests. Deterministic.
Claims: zip-meta-map.schema-validatedzip-meta-map.token-budgetszip-meta-map.ci-gatingzip-meta-map.246-testszip-meta-map.deterministic-output
hn technical msg.zip-meta-map.hn-post
Show HN: zip-meta-map — deterministic repo indexes for LLM agents. Same repo = same output, diffable in CI, token budgets for context windows. 246 tests, JSON Schema-validated, pip install zip-meta-map.
max 300 chars HN title should be separate and under 80 chars.
Claims: zip-meta-map.deterministic-outputzip-meta-map.ci-gatingzip-meta-map.token-budgetszip-meta-map.246-testszip-meta-map.schema-validated
x pragmatic msg.zip-meta-map.x-post
zip-meta-map: make any repo self-describing for LLMs. Deterministic output, token budgets, CI gating. 246 tests. pip install zip-meta-map
max 280 chars
Claims: zip-meta-map.deterministic-outputzip-meta-map.token-budgetszip-meta-map.ci-gatingzip-meta-map.246-tests
linkedin executive msg.zip-meta-map.linkedin-post
We built zip-meta-map to solve a specific problem: LLM agents need structured repo context, but directory listings waste tokens and drift silently. Our approach is deterministic indexes with CI gating — same repo, same output, every time. 246 tests enforce it.
max 700 chars
Claims: zip-meta-map.deterministic-outputzip-meta-map.token-budgetszip-meta-map.ci-gatingzip-meta-map.246-tests

Campaigns

zip-meta-map Launch

Tool: tool.zip-meta-map Audiences: aud.ci-maintainersaud.llm-toolchain-devs

Phase 1: Soft launch

readmeweb

Get the tool page and README polished before any external promotion.

Messages: msg.zip-meta-map.readme-snippetmsg.zip-meta-map.web-blurb

Phase 2: Community launch

hnx

HN Show + X post. Time for weekday morning US-East.

Messages: msg.zip-meta-map.hn-postmsg.zip-meta-map.x-post

Phase 3: Professional outreach

linkedin

LinkedIn post targeting engineering leaders and DevOps.

Messages: msg.zip-meta-map.linkedin-post