tesserakit-workflow
Validate Workflow Pack profile definitions: the governance schema that sits on top of the Tessera JobPack contract.
A Workflow Pack defines a governed multi-step workflow as a YAML file. This pack validates it:
- all steps have declared outputs (traceable)
- review gates reference real steps
- a recursion fence is declared
- evidence policy has hash-invariant steps (TOCTOU guard)
- no step references an undeclared adapter
Quickstart
tessera workflow validate --input examples/workflow/valid_codeops.workflow.yaml --output out/
open out/governance_report.md
What it checks
| Code | Severity | Description |
|---|---|---|
no_steps |
error | Workflow defines no steps |
review_gate_unknown_step |
error | Gate references a step that does not exist |
invalid_promotion_rule |
error | promotion_rule is not a known value |
capability_envelope_unknown_step |
error | Envelope references a step that does not exist |
missing_recursion_fence |
warning | No recursion fence defined (kernel-path mutation risk) |
promotion_without_review |
warning | promotion_rule: after_review but no gates defined |
undefined_adapter |
warning | Step uses adapter not listed in required_adapters |
missing_evidence_hash_invariant |
warning | No hash-invariant steps (TOCTOU risk) |
step_undefined_input |
warning | Step input not produced by any earlier step |
step_missing_outputs |
info | Step has no outputs (untraceable) |
Workflow Pack schema
name: my.workflow
version: "0.1"
steps:
- name: step_one
adapter: tessera_repo
outputs: [repo_map.jsonl]
- name: step_two
adapter: codegen
inputs: [repo_map.jsonl]
outputs: [patch.diff, patch_hash.txt]
required_adapters: [tessera_repo, codegen]
review_gates:
- after_step: step_two
label: human_review
evidence_policy:
hash_invariant_steps: [step_two]
recursion_fence:
protected_paths: [kernel/]
promotion_rule: after_review
Metadata
Release files for tesserakit-workflow 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| tesserakit_workflow-0.4.0.tar.gz | 6.8 kB | Without provenance | Details for tesserakit_workflow-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tesserakit_workflow-0.4.0-py3-none-any.whl | Python 3 | none | any | Details for tesserakit_workflow-0.4.0-py3-none-any.whl |
Total release size: 15.6 kB
Release files / tesserakit_workflow-0.4.0.tar.gz
| Download URL | tesserakit_workflow-0.4.0.tar.gz |
|---|---|
| Size | 6.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0ecd18a53688663dfb78656855e0651d46e82fc2ad7bdf1840d7b49c5c432610
|
|
BLAKE2b-256 checksum How to use checksums |
0783d09d01b36c645a69828c9b330add79cb8393adc8cc8bb398782c5c0b24dd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.5
|
Release files / tesserakit_workflow-0.4.0-py3-none-any.whl
| Download URL | tesserakit_workflow-0.4.0-py3-none-any.whl |
|---|---|
| Size | 8.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b79f023742d929fb31ddf8fcd390c8f73fbbb86c9a5ec25413f8f33e30e0b342
|
|
BLAKE2b-256 checksum How to use checksums |
af578e25fbffd59aeed95117a245b6dc91743c6e0067876e764239b709a58029
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.5
|
Security for tesserakit-workflow 0.4.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.