Reviewing an integrations prior-art artifact
You are the second half of a two-part gate. The first half already ran.
Do not re-check what the validator refuses. Every condition below names the rule that owns the
other half where one exists, and a finding you raise against a rule the gate already enforces is
noise that costs the author a cycle. If the gate did not run, say so and stop — a clean gate run is
a precondition of this review, not a substitute for it.
Your evidence
| source |
what it settles |
| the artifact under review |
everything below |
| the vocabulary map it was produced against |
whether the owed grid and the angle verdicts are right |
| the SCOPE and CLASSIFICATION the producer was handed |
whether meta.classification is a faithful transcription |
integrations-prior-art-survey/schemas/*.json |
what each field is FOR, in its description |
integrations-prior-art-survey/references/source-registry.yaml |
caps, orderings, bands, complete_listing, the excluded block |
integrations-prior-art-survey/references/angles/<angle>.md |
that angle's mechanism, sources and precondition |
integrations-prior-art-survey/references/absent-input-policy.md |
the nine catalog auth modes and which of them map to null — C9 |
integrations-prior-art-survey/references/category-vocabulary.md |
the seeded category vocabulary — C13 |
integrations-prior-art-survey/references/integration-vocabulary-map-guide.md |
the probe's three checks — C20 |
the FROZEN extract-queue.yaml, and the extract records themselves |
what extraction was asked to produce, and what it wrote — C26, C28 |
integrations-prior-art-survey/references/extraction-template-guide.md |
what each record field is FOR, field by field — C21-C25 |
integrations-prior-art-survey/references/synthesis-lenses.md |
the eight formulas and the denominator each divides by — C26-C29 |
integrations-prior-art-survey/references/synthesis-report-guide.md |
the report's eight fixed sections, and what does not go in it — C30 |
THIRTEEN sources, and NINE of them are PRODUCER-package paths you read rather than files this
package ships -- the schemas, the source registry, the angle references, the absent-input policy,
the category vocabulary, the vocabulary-map guide, the extraction template guide, the synthesis
lenses and the report guide. All nine. A review that reads only the artifact and the map can settle
the arithmetic and none of the vocabulary. The scope and classification are on the list because
meta.classification is a TRANSCRIPTION, and judged only against itself a fabricated value reads
exactly like a real one.
Conditions
Read references/conditions.md. Judge every condition that applies. A condition that does not
apply is recorded as such — silence is not a verdict.
Your verdict
Emit exactly one line, last:
VERDICT: approve
or
VERDICT: revise
revise requires at least one finding naming its condition. approve with findings attached is a
contradiction; if the findings are real, the verdict is revise.
Do not false-revise honest work. An artifact that records a small result honestly — three
candidates, an enumerated zero, a vacated angle with observable causes — is a correct artifact. The
survey's job is to record what is there, and a reviewer who treats a small number as a defect
teaches the next producer to pad.
1---2name: reviewing-integrations-prior-art-survey3description: Use when reviewing an integrations prior-art artifact — an integration vocabulary map, one angle's search output, one service's extract record, or the integration register and its report — before it is accepted. Judges what a deterministic gate cannot: whether a locator host really is the vendor's own, whether an evidence quote supports the claim drawn from it, whether an authority band is defensible for the page it points at, whether a record was deep-read first-party or restated from a catalog, whether each complexity component is the one the facts support, whether a lens denominator counts what was REACHED, and whether an admission or an absence was recorded truthfully. Emits exactly one verdict, approve or revise, with every finding tied to a numbered condition. Keywords: integrations prior art review, connector catalog review, descriptor evidence, vendor scope, coverage grid, integration register, prior-art reviewer.4---56# Reviewing an integrations prior-art artifact78You are the second half of a two-part gate. The first half already ran.910**Do not re-check what the validator refuses.** Every condition below names the rule that owns the11other half where one exists, and a finding you raise against a rule the gate already enforces is12noise that costs the author a cycle. If the gate did not run, say so and stop — a clean gate run is13a precondition of this review, not a substitute for it.1415## Your evidence1617| source | what it settles |18| --- | --- |19| the artifact under review | everything below |20| the vocabulary map it was produced against | whether the owed grid and the angle verdicts are right |21| the SCOPE and CLASSIFICATION the producer was handed | whether `meta.classification` is a faithful transcription |22| `integrations-prior-art-survey/schemas/*.json` | what each field is FOR, in its `description` |23| `integrations-prior-art-survey/references/source-registry.yaml` | caps, orderings, bands, `complete_listing`, the excluded block |24| `integrations-prior-art-survey/references/angles/<angle>.md` | that angle's mechanism, sources and precondition |25| `integrations-prior-art-survey/references/absent-input-policy.md` | the nine catalog auth modes and which of them map to `null` — C9 |26| `integrations-prior-art-survey/references/category-vocabulary.md` | the seeded `category` vocabulary — C13 |27| `integrations-prior-art-survey/references/integration-vocabulary-map-guide.md` | the probe's three checks — C20 |28| the FROZEN `extract-queue.yaml`, and the extract records themselves | what extraction was asked to produce, and what it wrote — C26, C28 |29| `integrations-prior-art-survey/references/extraction-template-guide.md` | what each record field is FOR, field by field — C21-C25 |30| `integrations-prior-art-survey/references/synthesis-lenses.md` | the eight formulas and the denominator each divides by — C26-C29 |31| `integrations-prior-art-survey/references/synthesis-report-guide.md` | the report's eight fixed sections, and what does not go in it — C30 |3233**THIRTEEN sources, and NINE of them are PRODUCER-package paths you read rather than files this34package ships** -- the schemas, the source registry, the angle references, the absent-input policy,35the category vocabulary, the vocabulary-map guide, the extraction template guide, the synthesis36lenses and the report guide. All nine. A review that reads only the artifact and the map can settle37the arithmetic and none of the vocabulary. The scope and classification are on the list because38`meta.classification` is a TRANSCRIPTION, and judged only against itself a fabricated value reads39exactly like a real one.4041## Conditions4243Read `references/conditions.md`. Judge every condition that applies. A condition that does not44apply is recorded as such — silence is not a verdict.4546## Your verdict4748Emit exactly one line, last:4950```51VERDICT: approve52```5354or5556```57VERDICT: revise58```5960`revise` requires at least one finding naming its condition. `approve` with findings attached is a61contradiction; if the findings are real, the verdict is `revise`.6263**Do not false-revise honest work.** An artifact that records a small result honestly — three64candidates, an enumerated zero, a vacated angle with observable causes — is a correct artifact. The65survey's job is to record what is there, and a reviewer who treats a small number as a defect66teaches the next producer to pad.
bm629