Skip to content
grid-diamondcutter

What the project does not claim

A useful project knows what it is not saying as clearly as what it is saying. This page lists thirteen claims the project has committed in writing not to make. Each one is enforced by a small checker that scans the repository on every change and fails if a forbidden claim slips into the public files.

If a future reader thinks the project is making one of these claims, they can point to this page and ask the maintainers to explain.

The list

These are paraphrased; the formal version lives in PREREGISTRATION.md and (for phase 2) in phase_2/PREREGISTRATION_PHASE_2.md.

  1. The simulator in this repository is not a substitute for production grid solvers like MATPOWER, PYPOWER, OpenDSS, GridLAB-D, or PSS®E. It is a small toy that demonstrates a method; it does not simulate a real grid.
  2. The adapter stub files do not actually call into real grid solvers unless the documentation for a specific commit says they do.
  3. The +0.832 coupling number in the demo is not a real-grid measurement. It is the correlation between two model voices the project authored.
  4. A result computed by this methodology is not a prediction of what the real grid will do without an explicit follow-on measurement that tests the forecasting claim.
  5. The methodology does not generalize across regulatory regions without adding a region-specific measurement first.
  6. The funding-gap modeling in the project is not a measurement of any specific company’s funding pipeline.
  7. A low rate of failed predictions in this project would be a bad sign, not a good one. It would suggest the predictions had been edited after the results came in.
  8. The closed components of the analytical pipeline (eirmath) are not required to evaluate any claim made in this repository.

The phase-2 extension adds:

  1. The phase-2 substrate is not modeled by physical grid simulators. It is a model of electricity-market behavior.
  2. No measurement on this site is investment advice in any jurisdiction.
  3. The phase-2 recognition criterion does not equal or imply any proprietary quantitative calibration.
  4. Public spot prices and volume do not exhaustively describe the phase-2 substrate. Private contracts, capacity markets, and ancillary services are out of scope.
  5. The orchestration tools the project happens to be authored on are not required to evaluate any claim made in this repository.

How they’re enforced

For each item above, there is a small checker in examples/voices/ whose filename starts with bound_defender_. Each checker scans the repository for the forbidden claim — for instance, the no-investment-advice checker looks for buy/sell/hold language attached to specific assets.

The checkers run on every change to the project. If any one fires, the change does not merge until either the forbidden claim is removed or the wording is reviewed.

A reader who wants to verify can run them locally:

Terminal window
git clone https://github.com/eir-inc/grid-diamondcutter
cd grid-diamondcutter
python -m pytest tests/test_voice_registry_contract.py