Charts Factory by ChartsMCP Alpha
Method

How a report is made — and what it does not claim

The Factory is a set of contracts, not a prompt library. Five gates decide what a report may say; what does not pass a gate is left out, not smoothed over.

Five gates

  1. 1 · Source Is the object and its evidence actually available? Missing is a valid result — the coverage matrix shows the gap instead of bridging it.
  2. 2 · Semantics Definitions, periods and units are resolved before anything is drawn. A number without a period is not a number.
  3. 3 · Pack Each pack has fixed questions and slots. The method is standardised; the interpretation follows the data, not a template.
  4. 4 · Render Charts come from the engine, not from hand-drawn markup. What you see on this site is the artifact that is downloaded, byte for byte.
  5. 5 · Export A format is offered only when that artifact really exists. The download list is read from the store, not maintained by hand.

Three public states

Only these three. Roadmap words like “build now” describe our plans, not what you can use.

Live

Self-service within a defined perimeter; known limits are shown.

Pilot · limited objects

Runs for defined objects only, or needs a review step.

Preview · no self-service

Publicly explainable, but no generic run button.

What stays separate

A report keeps three kinds of statement apart, and says which is which.

Observed

A number from the sources, with its period and unit.

Attributed

A statement someone else made — quoted, with its source anchor. “Management attributes the increase to pricing” is not the same as “pricing caused the increase”.

Modelled

A value derived by a documented calculation, never presented as a measurement.

Addresses and indexing

Language is part of the address, never a hidden preference. An address is a promise: it is issued once and stays.

Indexed

Home, explorer, packs, objects, reports and slides.

factory.chartsmcp.com/en/method/ factory.chartsmcp.com/de/method/ factory.chartsmcp.com/ja/method/ factory.chartsmcp.com/fa/method/

Not indexed

Build states (wrong by tomorrow), the review tools, the API and the raw decks — the last would compete with their own report page.

robots.txt sitemap.xml

What is measured

Four numbers, no page views. No cookie, no identifier, no address — the question is which artifact triggers which next action, not who did it.

906 Footer clicks last 30 days
0 Builds started last 30 days
0 Builds decided last 30 days
0 Foreign objects last 30 days

The one that matters: reports for objects we did not choose. A report with a few hundred readers that produces several foreign objects is stronger than a viral one that produces none.

Use the result — then reproduce it

The report is the distribution artifact. These four actions are part of its manifest, not a marketing block added afterwards.

1 · Create this report for another object Primary handoff 2 · Built with Charts MCP Method, engine, provenance
3 · Improve this pack on GitHub Public pack repository — launch dependency
4 · Run privately in Charts Desk Private sources, persistent state