A autogenschema-gate1.1.0

Schema Gate

Get card

Download

schema-gate@1.1.0.yaml

Clone

npx -y darkprint clone schema-gate@1.1.0

There is no repository and no history behind a card. Download hands you the document as it stands, and Clone fetches the same document by name.

↓ 2 downloads

Check the candidate record against the registered schema plus any assertions attached for this run, pass only what clears both, and emit the violation list for the rest.

Cardtype ·Validation phase ·Testing will_not ·1 promised

used in 2 blueprints

Specification

83 words · handed to the agent

Check the normalized record you are handed against the schema registered as schema-registry://forge-record@2, and against any extra rules handed to you alongside it cross-field invariants included. Emit the record byte-for-byte unchanged on accepted only when it clears both; a field the schema does not name is a failure, not a tolerance. Otherwise emit one entry per breach on violations, each naming the field and the specific constraint it broke, and stop at twenty-five entries so one unparseable batch cannot flood whatever repairs them.

Interfaces

2 in · 2 out

Inputs

Inputs declared by this node card
Name	Data type	Required	Description
candidate	json	required	The normalized record on its way into a system that expects a guarantee.
assertions	json	optional	Extra per-run rules checked on top of the schema, such as cross-field invariants.

Outputs

Outputs declared by this node card
Name	Data type	Description
accepted	json	The record unchanged, now carrying the guarantee that it matches the schema.
violations	json	Field-level failures, one entry per breach, for the repair path to work from.

Dependencies

normalize

The upstream nodes this card expects to receive from. Whenever a blueprint pins this card, each name is checked against a real edge in that graph. A name without a link is not a published card; it refers to a node inside some graph.

Card values

17 declared

Identitycard spec →

Who the node is. The id is the key the DOT pins.

id: schema-gate
name: Schema Gate
type: validation
phases: Testing

Behaviourcard spec →

What it does, and the prose the agent is handed when the graph runs.

action28 words: Check the candidate record against the registered schema plus any assertions attached for this run, pass only what clears both, and emit the violation list for the rest.
spec83 words: Check the normalized record you are handed against the schema registered as schema-registry://forge-record@2, and against any extra rules handed to you alongside it cross-field invariants included. Emit the record byte-for-byte unchanged on accepted only when it clears both; a field the schema does not name is a failure, not a tolerance. Otherwise emit one entry per breach on violations, each naming the field and the specific constraint it broke, and stop at twenty-five entries so one unparseable batch cannot flood whatever repairs them.in full above
model: claude-haiku-4-5
agent: Validator
skill: skills/schema-gate.md
tools: none
mcp: none
params: strict: true, schema_ref: schema-registry://forge-record@2, max_violations: 25

Interfacescard spec →

What arrives, what leaves, which nodes it expects to hear from, and what may not.

inputs: candidate : json, assertions : json
outputs: accepted : json, violations : json
dependencies: normalize
cannot: no type is refused
will_not: edit a record to make it conform

Evaluation metadatacard spec →

The keys the static analysis reads. Nothing here instructs the agent.

risk_markers: none
notes32 words: max_violations truncates the report on genuinely broken input so a single unparseable batch cannot flood the repair loop. assertions is optional: with none attached the gate behaves exactly as version 1.0.0 does.

Service fieldscard spec →

The card's own version, and who wrote it.

version: 1.1.0
author: autogen
provenance: not stated

Definitions for every card field

Version history

2 versions published

schema-gate@1.1.0currentsha256:f3d48ec693c5f27083efff693c99010d9c9227b0876a24b4e3382cbabc7385a2
pinned bySchema Forge ETLautogen/schema-forge-etl
minor1.0.0 → 1.1.0something was added; old pins still resolve
- optional input assertions was added
- parameter max_violations was added
- spec changed, the instruction handed to the agent is different
- parameter schema_ref changed: "schema-registry://warehouse-record@3" → "schema-registry://forge-record@2"
- action wording changed
- notes changed
schema-gate@1.0.0sha256:da60cb1fc03eff9e3fb9eba31540d6470546c07b1402fa5f3cfbb352b809d3f5
pinned byNightly Data Janitorautogen/nightly-data-janitor

A digest is a fingerprint (SHA-256) of the card's content, computed without the author and provenance fields. The same card from two people gets the same digest; any edit gets a new one.

Community notes (0)

No notes yet.

Nobody has posted about this node card yet.