Conversation
…ture Introduces the Option B satellite schema architecture: two new normative artifacts (form-definition and execution-mapping) linked to the catalog by serviceId, separating citizen form generation and n8n orchestration concerns from the core procedure definition. Changes by artifact: - 0-document-control: expand objective to full pipeline; add satellite schemas as draft normative artifacts in §0.3 - 1-architecture-and-scope: extend to 5 layers; fix scope exclusion for form fields; add §1.5 documenting satellite architecture and Option B decision; add full pipeline diagram in §1.4 - 2-conformance-and-governance: consolidate normative language definition; add Form Profile and Execution Profile; define satellite versioning policy - 3-information-model-and-field-dictionary: fix SHOULD→MUST for documentsRequired fields (BR alignment); cross-reference BR catalog from §3.5; add §3.6 and §3.7 for satellite model references - 4-publication-profile-and-quality-gates: clarify approved_auto as sole publishable reviewStatus; add satellite consistency policy to checklist - 5-workflow-execution-mapping: full rewrite as normative companion to execution-mapping schema; add field table, action vocabulary, complete state machine with rejected/cancelled/complement branches - 6-business-rules-catalog: resolve BR-008 ambiguity (approved_auto only); clarify BR-010 escalation logic; add BR-011 satellite referential integrity - glossary: add 11 new terms covering satellite schema, serviceId, pipeline, building block, form definition, execution mapping, design-time contract, form/execution profiles, normalizationConfidence, qualityFlag, frictionScore - examples/invalid-explained.json: fix structural bug (_comment/_fails removed from root, violated additionalProperties:false) - examples/invalid-explained.md: new companion annotation file documenting expected BR violations per profile Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
form-definition.schema.json: - Fields: serviceId, catalogSchemaVersion, sections[], fields[] - Field types: text, textarea, number, date, select, multiselect, boolean, file, hidden - Per-field: validation (minLength, maxLength, pattern, min, max), options (select/multiselect), fileConstraints (acceptedTypes, maxSizeKb, multiple), conditional display logic (condition object), mapsToDocumentTypeCode, mapsToWorkflowStepId - Pattern constraint on fieldId: ^field_[a-z0-9_-]+$ execution-mapping.schema.json: - Fields: serviceId, catalogSchemaVersion, mappingVersion, steps[] - Per-step: action (11-value enum aligned with catalog stepType), connector, inputMapping, outputMapping, retryPolicy, timeout, humanTask (assigneeRole, dueDays, instructions), onFailure - Conditional: action=custom requires connector (if/then) - onFailure enum: escalate, reject, suspend Examples (based on MID-EXAMPLE-002, 3-step procedure): - valid-form-definition.json: 6 fields across 2 sections, conditional field (num_stat shown for entreprise only), file fields with constraints and documentTypeCode mapping - valid-execution-mapping.json: case_intake (form connector), document_check (http + humanTask), notification_send (email); inputMapping/outputMapping with template variable syntax Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR revises the entire specification to reflect the new 5-stage pipeline vision and the Option B satellite schema architecture decision.
form-definition,execution-mapping) linked to the catalog byserviceId, separating form generation and n8n orchestration concerns from the core procedure definitionexecution-mapping.schema.jsonwith field table, action vocabulary, and a complete state machine (including rejected/cancelled/complement branches)approved_autois now the only publishable review status (removes untestable governance qualifier)serviceIdinvalid-explained.jsonwas structurally invalid due to_comment/_failsfields violatingadditionalProperties: false; annotations moved to companion.mdfileFiles changed
0-document-control.md1-architecture-and-scope.md2-conformance-and-governance.md3-information-model-and-field-dictionary.md4-publication-profile-and-quality-gates.md5-workflow-execution-mapping.md6-business-rules-catalog.mdglossary.mdexamples/invalid-explained.jsonexamples/invalid-explained.mdNext steps after merge
schema/form-definition.schema.json(v0.1 draft)schema/execution-mapping.schema.json(v0.1 draft)2.0.0-draft.3Test plan
invalid-explained.jsonpasses structural validation but fails BR-004, BR-008, BR-005 under Public API profilevalid-internal.jsonpasses Internal Profile, blocked by Public API Profilevalid-public.jsonpasses both profiles🤖 Generated with Claude Code