feat(2.3.0): Algorithm Cards — optional governance wrapper for algori… - #13
Merged
Conversation
…thms behind resource targets Add a new OPTIONAL artifact category, Algorithm Cards, that supplies governance metadata (intent, IO contract, ownership, lifecycle, validation, optional extensions for ML/crypto/privacy/risk/prompt) for one algorithm invoked behind a resource target. Cards live in the package's algorithms/ folder and validate against the new algorithm-card schema. Resource mapping targets gain an optional algorithm_card reference. Fully additive, backward-compatible — every package valid under 2.2.x stays valid under 2.3.0. Algorithm Cards EXTEND the Resources cornerstone — they do NOT become a fifth cornerstone. The four cornerstones (BPMN, DMN, CMMN, Resources + Mapping) remain authoritative and unchanged. Additions: - specification/13-algorithm-cards.md (new normative chapter) - schemas/algorithm-card.schema.json (new normative schema) - specification/11-semantic-validation.md: new SEM-012 rule - specification/10-conformance-checklist.md: new optional conformance block - specification/02-process-cornerstones.md: clarifying note - README.md, CHANGELOG.md, VERSION: 2.2.0 -> 2.3.0 - schemas/uapf-manifest.schema.json: optional algorithm_cards + paths.algorithms - schemas/resource-mapping.schema.json: optional target.algorithm_card - examples/approve-expense-l4: one Card added to demonstrate the feature - .github/workflows/validate.yml: card validation step
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.
…thms behind resource targets
Add a new OPTIONAL artifact category, Algorithm Cards, that supplies governance metadata (intent, IO contract, ownership, lifecycle, validation, optional extensions for ML/crypto/privacy/risk/prompt) for one algorithm invoked behind a resource target. Cards live in the package's algorithms/ folder and validate against the new algorithm-card schema. Resource mapping targets gain an optional algorithm_card reference. Fully additive, backward-compatible — every package valid under 2.2.x stays valid under 2.3.0.
Algorithm Cards EXTEND the Resources cornerstone — they do NOT become a fifth cornerstone. The four cornerstones (BPMN, DMN, CMMN, Resources
Additions: