Pre-submit intake checks run
-Workstream runs pre-submit checks from the locked project pre-submit checker policy before creating a submission row. Preflight failures return PreSubmitCheckResponse details. Blocked submission-create attempts return pre_submission_checker_failed with pass/fail/warning details.
+Workstream runs one effective pre-submission plan against the uploaded outer ZIP in bounded scratch before creating a submission. Failed preparation returns bounded same-request pre_submission_checker_failed details; there is no standalone preflight route.
no submission yet
no checker run yet
@@ -525,29 +525,30 @@ Pre-submit intake checks run
Submission packet is created
-After blocking pre-submit checks pass, Workstream creates the submission with summary, package reference, artifact hashes, evidence references, and attestation.
+Verified admission is published
+After blocking pre-submit checks pass, Workstream stores the outer ZIP once, independently reads it back, and publishes a capacity-charged ready admission bound to the server-generated manifest and pre-submit evidence.
-
Submission v1
- EvidenceItem
- artifact_hash_manifest
+ SubmissionBundleAdmission: ready
+ ArtifactContent
+ SubmissionBundleManifest
Submission is finalized
-The server records finalization against the task's server-owned guide and policy context, finalizes evidence rows, and schedules the checker run.
+Submission consumes the admission
+Under fresh human and fixed-service authority, one transaction locks the ready admission and task context, creates the immutable Submission and exact artifact binding, and marks the admission consumed.
-
finalized_at
- submission_finalized
+ Submission v1
+ ArtifactBinding
+ admission: consumed
Automatic checkers execute
-Registered checkers run against the exact finalized submission, package hash, artifacts, and policy context.
+Registered post-submit checkers materialize and rehash the exact immutable Submission binding, manifest, and locked policy context.
CheckerRun
CheckerResult
@@ -599,7 +600,7 @@ Durable Records Created Along The Way
Submission Packet
- Submission version, package URI, package hash, artifact hash manifest, evidence rows.
+ Submission version, consumed ready admission, immutable ArtifactBinding/ArtifactContent identity, server-generated SubmissionBundleManifest, and pre-submit evidence set.
Checker Trail
@@ -607,7 +608,7 @@
Durable Records Created Along The Way
Audit Events
- Task creation, status changes, submission finalization, checker gate start/pass/block.
+ Task creation, status changes, admission publication/consumption, checker gate start/pass/block.
Visibility Rules
@@ -631,16 +632,16 @@ Guide activation fails if the immutable guide source snapshot, guide sufficiency report, submission artifact policy, effective project submission artifact policy hash, project pre-submit checker compiled bundle hash, approved generated project post-submit checker policy with matching provenance, or required review and revision policy context is missing.
Pre-submit intake failures create no submission row or submission version.
Revision resubmission states are limited to needs_revision in v0.1.
- Submission packet does not carry guide or policy versions from the contributor.
- Submission finalization records against the task's server-owned guide and policy context.
- Evidence rows finalize with the submission.
- Checker runs bind to submission version, package hash, and artifact hashes.
+ Submission input does not carry provider references, package hashes, manifests, guide versions, or policy versions from the contributor.
+ Submission creation consumes one verified ready admission against the task's server-owned guide and policy context.
+ Pre-submit evidence binds to the same manifest and admission.
+ Checker runs bind to the immutable Submission, ArtifactBinding, ArtifactContent, and server-generated manifest identities.
Duplicate checker results fail the real API drill.
Contributor-facing review decisions stay accept, needs_revision, and reject.
` | `
Hard Invariants
-
diff --git a/docs/decision_0011_submission_artifact_policy_drives_pre_submit.md b/docs/decision_0011_submission_artifact_policy_drives_pre_submit.md
index e14abeb9b..f7dae98e9 100644
--- a/docs/decision_0011_submission_artifact_policy_drives_pre_submit.md
+++ b/docs/decision_0011_submission_artifact_policy_drives_pre_submit.md
@@ -137,6 +137,26 @@ PreSubmitCheckerPolicy =
trusted compiler output from EffectiveProjectSubmissionArtifactPolicy
```
+Runtime execution uses one code-owned, versioned
+`PreSubmissionCheckerCatalogue`. The catalogue contains both Workstream-owned
+artifact-custody/default checks and the constrained primitives referenced by a
+locked project policy. Compilation produces one ordered
+`EffectivePreSubmissionExecutionPlan`; it does not create a project-specific
+checker API or registry.
+
+Every catalogue entry declares a stable checker ID and version, owner, phase,
+order/dependencies, classification, typed input capability, bounded limits and
+result schema, policy trace, and `enabled|disabled` operational state. In v0.1,
+availability is startup-validated, versioned deployment configuration—not a
+contributor, Project Manager, task, or project-policy toggle.
+
+- disabling a mandatory security, integrity, or contributor-accountability
+ entry makes preparation fail closed as infrastructure unavailable;
+- disabling an advisory entry allows the rest of the plan to run but records
+ that disabled entry in the bounded execution manifest;
+- a locked project-required rule cannot be disabled at runtime; changing it
+ requires a new approved policy lineage.
+
`SubmissionArtifactPolicyDerivationAgent` produces the artifact-intake contract
at project setup time. Workstream's trusted checker compiler builds and
validates the constrained checker specification and persists the project-level
@@ -191,6 +211,27 @@ Approved pre-submit checker primitives include:
- `require_packaging`
- `warn_low_quality_generated_artifact`
+The catalogue also registers the non-policy artifact-custody prelude already
+owned by ART: outer-ZIP validation, archive/path/resource safety, exact archive
+identity, semantic-manifest identity, executable normalization,
+unchanged-revision rejection, and sealed scratch-tree integrity. These gates
+produce trusted inputs for policy primitives and cannot be removed or
+downgraded by the compiler.
+
+The stable v0.1 platform IDs are defined by the active ART chunk contract and
+include `artifact.outer_zip.valid`, `artifact.archive.paths_safe`,
+`artifact.archive.entries_safe`, `artifact.archive.resources_bounded`,
+`artifact.archive.integrity_verified`, `artifact.archive.identity_computed`,
+`artifact.manifest.semantic_identity_computed`,
+`artifact.manifest.executable_normalized`,
+`artifact.revision.content_changed`,
+`artifact.scratch.sealed_tree_verified`,
+`submission.packet.required_fields`,
+`submission.attestation.required_topics`,
+`artifact.sensitive_paths.high_confidence`, and
+`artifact.quality.placeholder_signal`. Renaming or removing one requires a new
+catalogue version and migration/replay decision; aliases are not accepted.
+
The trusted compiler must keep `warn_low_quality_generated_artifact`
warning-only; escalating that primitive to blocking is rejected because it would
change contributor-facing intake semantics.
@@ -212,33 +253,26 @@ Blocking pre-submit failures prevent submission creation. When blocking pre-subm
structured checker result for project operators
- the response does not use review decision values: `accept`, `needs_revision`, or `reject`
-Pre-submit has two API contracts:
-
-```text
-POST /tasks/{id}/submission-precheck
-200 PreSubmitCheckResponse
-{
- "status": "failed",
- "eligible_to_submit": false,
- "results": [...]
-}
-```
+The legacy standalone `/tasks/{id}/submission-precheck` contract is superseded.
+Pre-submit checks now run only inside the continuous submission-bundle
+preparation request against the exact uploaded ZIP in bounded scratch:
```text
-POST /tasks/{id}/submissions
+POST /api/v1/tasks/{id}/submission-bundle-preparations
422 DomainError
{
"code": "pre_submission_checker_failed",
- "details": {
- "status": "failed",
- "eligible_to_submit": false,
- "results": [...]
- }
+ "details": {"status": "failed", "eligible_to_submit": false, "results": [...]}
}
```
-`pre_submission_checker_failed` is the submission-creation error code. It is not
-a review decision and is not the response type for the preflight endpoint.
+There is no independently invocable precheck route and no reusable client-owned
+manifest input. The bounded result is returned only to the authorized actor in
+that same request. A passing preparation later returns an admission identity;
+`POST /api/v1/tasks/{id}/submissions` consumes that verified ready admission under its
+separate fresh authority and does not rerun scratch-bound checks.
+
+`pre_submission_checker_failed` is an intake error code, not a review decision.
Pre-submit checks are authoritative for submission intake. They are not authoritative proof for human review readiness. Review readiness still requires post-submit internal checker runs against a finalized submission.
@@ -274,17 +308,18 @@ separation before this ADR can be closed as fully implemented.
## Default Workstream Submission Artifact Rules
-Every submission must include:
+Contributor preparation supplies:
- summary
-- package hash when a package reference is supplied
-- artifact hash manifest
- contributor attestation
+- exactly one outer ZIP containing every required work/evidence file
-Every artifact manifest entry must include:
+Workstream—not the client—computes and binds:
-- artifact name or relative path
-- artifact hash
+- exact outer-ZIP SHA-256 and byte count
+- the canonical semantic manifest and every entry hash/byte count
+- required-file/evidence facts from that manifest and sealed workspace
+- the immutable pre-submit evidence set and verified ready-admission identity
Every artifact path must be safe:
@@ -297,7 +332,7 @@ Uploaded artifacts and storage-backed evidence require `sha256:<64 lowercase hex
Persisted storage references must be Workstream-issued opaque object references or validated object-storage adapter references. Raw signed URLs, credential-bearing URLs, query strings, local filesystem paths, bucket secrets, and token-bearing references are rejected before persistence. Normalization is allowed only for already-approved adapter references that contain no secrets, credentials, or query material.
-Default forbidden artifacts remain blocked even if a project policy accidentally lists them as required. A required artifact that violates the default forbidden policy is a project setup defect.
+Default forbidden artifacts remain blocked even if a project policy accidentally lists them as required. A required artifact that violates the default forbidden policy is a project setup defect. Universal blocking patterns must be narrowly high-confidence. Broad name heuristics such as `token*`, `secret*`, `credential*`, or dependency-directory names require explicit classification as advisory or project-specific unless the exact match proves a generic custody risk.
The effective policy merge is deterministic:
diff --git a/docs/glossary.md b/docs/glossary.md
index 1c6b54918..80dec9224 100644
--- a/docs/glossary.md
+++ b/docs/glossary.md
@@ -225,11 +225,11 @@ The deterministic merge of Workstream's default submission artifact policy and t
## Pre-Submit Checker Policy
-The server-generated project checker matrix produced from the effective project submission artifact policy, persisted with a compiled bundle hash, and locked by tasks before they enter the contributor pipeline. It runs before Workstream creates a submission row or submission version. The preflight endpoint returns `PreSubmitCheckResponse`; a blocked submission-create attempt returns `pre_submission_checker_failed` with structured pass/fail/warning details. Neither path returns review decision values: `accept`, `needs_revision`, or `reject`.
+The server-generated project checker matrix produced from the effective project submission artifact policy and one immutable default-catalogue snapshot. The compiled bundle embeds the catalogue version, canonical manifest digest, ordered entry ID/version/configuration hashes, and enabled/disabled state. Its compiled bundle hash therefore commits transitively to that exact snapshot, and each task locks that hash before entering the contributor pipeline. Runtime uses the same snapshot to derive the effective-plan hash. It runs against the uploaded ZIP in bounded scratch before Workstream creates a submission. A failed preparation returns `pre_submission_checker_failed` with bounded same-request details. There is no standalone preflight route, and results never use review decision values: `accept`, `needs_revision`, or `reject`.
## pre_submission_checker_failed
-The contributor-facing domain error code returned when a submission-create attempt is blocked by pre-submit checks. It includes structured pass/fail/warning details in the error details and is not a review decision. It must not be stored as `accept`, `needs_revision`, or `reject`. The preflight endpoint returns `PreSubmitCheckResponse` instead of this error code.
+The contributor-facing domain error code returned when submission-bundle preparation is blocked by pre-submit checks. It includes bounded structured pass/fail/warning details in the same response and is not a review decision. It must not be stored as `accept`, `needs_revision`, or `reject`.
## Task
@@ -267,7 +267,11 @@ review, compensate, and audit work.
## Submission Packet
-The contributor's submitted output plus summary, artifacts, evidence references, hashes, and metadata. Workstream assigns the submission version server-side after blocking pre-submit checks pass.
+The contributor supplies a summary, accountability attestation, and one outer
+ZIP containing every required output/evidence file. Workstream derives the
+archive hash/size, semantic manifest, evidence facts, verified admission,
+artifact binding, and immutable Submission version server-side. Clients do not
+supply canonical hashes, manifests, provider references, or content IDs.
## Checker
diff --git a/docs/operations_project_operating_manual.md b/docs/operations_project_operating_manual.md
index 41ef74619..0a1f030aa 100644
--- a/docs/operations_project_operating_manual.md
+++ b/docs/operations_project_operating_manual.md
@@ -246,13 +246,14 @@ Before locking a submission packet:
- task is assigned to submitter
- summary exists
-- output package or reference exists
-- evidence exists
+- exactly one outer ZIP is uploaded through submission-bundle preparation
+- every project-required output/evidence file exists inside that ZIP
+- contributor attestation exists
- revision replay exists when task was previously `NEEDS_REVISION`
- effective project submission artifact policy is loaded
- generated project pre-submit checker policy runs
-- preflight failures return `PreSubmitCheckResponse(status="failed", eligible_to_submit=false, results=[...])`
-- blocked submission-create attempts return `pre_submission_checker_failed` with structured pass/fail/warning details
+- failed submission-bundle preparation returns `pre_submission_checker_failed` with bounded same-request status, eligibility, and pass/fail/warning details
+- no standalone preflight endpoint or client-owned manifest can reproduce the authoritative result
- no submission row is created until blocking pre-submit checks pass
- successful submission creation stamps the immutable submission boundary and queues the Celery pre-review gate
- `/finalize` is an Operator repair/requeue endpoint under
diff --git a/docs/product_first_user_flows.md b/docs/product_first_user_flows.md
index fba60f66e..76f332919 100644
--- a/docs/product_first_user_flows.md
+++ b/docs/product_first_user_flows.md
@@ -90,13 +90,14 @@ Acceptance:
## Flow 3: Contributor Submits Work
1. Contributor opens assigned task.
-2. Contributor attaches output files or links.
-3. Contributor attaches evidence.
-4. Contributor writes submission notes.
-5. Workstream executes the task's locked project `PreSubmitCheckerPolicy`.
-6. Preflight failures return `PreSubmitCheckResponse`; blocked submission-create attempts return `pre_submission_checker_failed` with structured pass/fail/warning details and create no submission.
-7. When blocking pre-submit checks pass, Contributor submits packet.
-8. Task enters `SUBMITTED`.
+2. Contributor uploads one outer ZIP containing every required output and evidence file.
+3. Contributor writes the required summary and attestation.
+4. Workstream safely inspects and manifests the ZIP in bounded private scratch.
+5. Workstream executes the single effective pre-submission plan: platform defaults plus the task-locked Project Guide policy.
+6. Failure returns bounded same-request `pre_submission_checker_failed` details and creates no submission or durable artifact.
+7. Passing bytes are stored and independently verified, producing a ready admission.
+8. Contributor creates the immutable Submission by consuming that admission under fresh authority.
+9. Task enters `SUBMITTED`.
Acceptance:
diff --git a/docs/spec_artifact_storage_service.md b/docs/spec_artifact_storage_service.md
index 675ce99cd..754eb76e4 100644
--- a/docs/spec_artifact_storage_service.md
+++ b/docs/spec_artifact_storage_service.md
@@ -1099,7 +1099,33 @@ only the manager-owned directory write bit after no-follow ownership/type
validation, then remove the tree; archive-supplied modes are never applied.
Mandatory platform and locked Project Guide checks consume that same read-only
-scratch tree. Infrastructure exhaustion returns:
+scratch tree as one ordered `EffectivePreSubmissionExecutionPlan` assembled from
+the central versioned `PreSubmissionCheckerCatalogue`:
+
+```text
+artifact custody/safety phase
+-> Workstream default policy phase
+-> locked Project Guide policy phase
+-> one bounded result/evidence envelope
+```
+
+The catalogue is the only name/version/dispatch registry. Each entry declares
+its classification, phase/order/dependencies, typed inputs, resource budget,
+stable result, policy provenance, and explicit `enabled|disabled` state.
+Startup validation rejects missing dependencies, duplicate IDs/versions,
+unknown policy primitives, invalid ordering, and any configuration that would
+treat a disabled mandatory entry as passing. A disabled mandatory security,
+integrity, or accountability entry fails preparation closed before durable or
+provider effects. A disabled advisory entry is recorded and skipped. Project
+policy and task parameters cannot toggle catalogue availability.
+
+ART's already implemented ZIP safety, manifest, executable, and change gates
+are registered capabilities in this plan; 04B does not reimplement them. The
+locked project policy consumes the server-derived manifest and sealed workspace
+through the same execution API. It may require `task.toml` or any other
+project-specific file, but no such filename is a Workstream universal default.
+
+Infrastructure exhaustion or mandatory catalogue unavailability returns:
```text
HTTP 503
@@ -1617,7 +1643,7 @@ bytes in PostgreSQL.
### Remaining v0.1 dependency order
The pre-submit checker materializer is a mandatory part of preparation, so its
-fixed-service AUTH activation must merge after hidden ART-04B and before
+fixed-service AUTH activation must merge after hidden ART-04B1-04B3 and before
contributor preparation is activated. Post-submit materialization and checker
output actions remain a later activation after ART-06A/06B. This ordering
prevents a live contributor route whose mandatory checker read is unavailable.
diff --git a/docs/spec_authorization_service.md b/docs/spec_authorization_service.md
index c9ad7e2dd..486d0e0c7 100644
--- a/docs/spec_authorization_service.md
+++ b/docs/spec_authorization_service.md
@@ -408,8 +408,8 @@ The paired artifact hidden-behavior matrix is closed:
| `WS-ART-001-02D` | Operator binding/replica/receipt/verification-job/recovery-attempt/audit reads; the operations-domain `operations.artifact_storage_admission.read` action mapped to `operations.status.read`; verification retry; `artifact.verification.execute`; `artifact.pending_work.scan`; and `artifact.put_attempt.resolve` |
| `WS-ART-001-03` | Hidden guide behavior for `artifact.guide_source.ingest -> artifact.guide_source.ingest`, `artifact.guide_source.read -> artifact.guide_source.read`, and `artifact.guide_source.binding.create -> artifact.binding.create`; AUTH activation custody is split between WS-XINT-002-04A and 04B below |
| `WS-ART-001-04A` historical baseline | the former multi-step upload authority had no route/command and is deleted from the live catalogue by WS-XINT-002-01 without compatibility aliases |
-| `WS-ART-001-04A1` through `04C2` | one hidden `artifact.submission_bundle.prepare` surface mapped to `submission.create`; 04B depends on 04A3, XINT-002-06A activates its fixed pre-submit materializer before 04C1, and the contributor action remains unavailable until complete 04C2 evidence and WS-XINT-002-05A |
-| `WS-ART-001-04B` | `artifact.pre_submit.checker_input.materialize` mapped to `artifact.checker_input.materialize` |
+| `WS-ART-001-04A1` through `04C2` | one hidden `artifact.submission_bundle.prepare` surface mapped to `submission.create`; 04A4 removes the legacy standalone precheck after 04A3, 04B1-04B3 implement the sole catalogue/materialization/evidence path, XINT-002-06A activates its fixed pre-submit materializer before 04C1, and the contributor action remains unavailable until complete 04C2 evidence and WS-XINT-002-05A |
+| `WS-ART-001-04B2` and `04B3` | hidden `artifact.pre_submit.checker_input.materialize` resource/guard usage mapped to `artifact.checker_input.materialize`; 04B2 owns exact sealed materialization and 04B3 consumes it in the complete effective plan |
| `WS-ART-001-05` | `artifact.submission.binding.create` mapped to `artifact.binding.create` |
| `WS-ART-001-06A` | `artifact.post_submit.checker_input.materialize` mapped to `artifact.checker_input.materialize` |
| `WS-ART-001-06B` | `artifact.checker_output.write` mapped to `artifact.checker_output.write`; `artifact.checker_output.binding.create` mapped to `artifact.binding.create`, both using the checker-run resource |
@@ -417,8 +417,8 @@ The paired artifact hidden-behavior matrix is closed:
WS-XINT-002-01 deletes the former multi-step authority and registers planned
`artifact.submission_bundle.prepare -> submission.create`. No ART implementation
may execute that ActionId while it remains planned. The mandatory order is
-ART-04A1 -> 04A2 -> 04A3 -> 04B -> XINT-002-06A -> ART-04C1 -> 04C2 ->
-XINT-002-05A. This ensures fixed-service pre-submit materialization is active
+ART-04A1 -> 04A2 -> 04A3 -> PLAN4 -> 04A4 -> 04B1 -> 04B2 -> 04B3 ->
+XINT-002-06A -> ART-04C1 -> 04C2 -> XINT-002-05A. This ensures fixed-service pre-submit materialization is active
before contributor preparation can become live.
WS-XINT-002-04A activates only `artifact.guide_source.ingest`. The existing
@@ -508,7 +508,7 @@ remain planned and unavailable, and add no migration.
| `artifact.verification.execute` | `artifact.verification.execute` | fixed verifier service | verification job | `02D` |
| `artifact.pending_work.scan` | `artifact.pending_work.scan` | fixed scheduler service | system pending-work scope | `02D` |
| `artifact.put_attempt.resolve` | `artifact.put_attempt.resolve` | fixed put-resolver service | put attempt | `02D` |
-| `artifact.pre_submit.checker_input.materialize` | `artifact.checker_input.materialize` | fixed materializer service | task plus current process-local prepared-bundle generation; no scratch path/handle is serialized | `04B` |
+| `artifact.pre_submit.checker_input.materialize` | `artifact.checker_input.materialize` | fixed materializer service | task plus current process-local prepared-bundle generation; no scratch path/handle is serialized | `04B2/04B3` |
| `artifact.post_submit.checker_input.materialize` | `artifact.checker_input.materialize` | fixed materializer service | checker run and immutable bindings | `06A` |
| `artifact.checker_output.write` | `artifact.checker_output.write` | fixed checker-output service | checker run | `06B` |
| `artifact.review_packet.materialize` | `artifact.review_packet.materialize` | fixed materializer service | exact active lease and Submission packet | `07A` |
diff --git a/docs/spec_chunk_8_submission_artifact_policy_checkers.md b/docs/spec_chunk_8_submission_artifact_policy_checkers.md
index f9b11d344..2ff26ed8d 100644
--- a/docs/spec_chunk_8_submission_artifact_policy_checkers.md
+++ b/docs/spec_chunk_8_submission_artifact_policy_checkers.md
@@ -3,6 +3,13 @@
> Historical implementation record. It does not define current sequencing or
> status; later canonical specifications and merged behavior take precedence.
+Current submission-bundle preparation does not revive this document's
+caller-owned precheck surface or standalone registry. WS-ART-001 PLAN4 and
+04B1-04B3 place these constrained policy checks in the single versioned
+pre-submission catalogue after ART-owned outer-ZIP custody gates, using the
+server-derived manifest and sealed workspace. Catalogue availability follows
+the fail-closed mandatory/advisory semantics in ADR 0011.
+
## Purpose
Chunk 8 expands the checker registry from the first structural runner into the first policy-aware submission artifact gate.
@@ -222,13 +229,14 @@ WorkstreamDefaultSubmissionArtifactPolicy
Workstream defaults are non-bypassable. Project policy can add required artifacts, evidence requirements, stricter forbidden patterns, and packaging rules, but it cannot remove hash requirements, allow unsafe storage references, require forbidden files, or downgrade blocking defaults.
-Blocking pre-submit failures prevent submission creation. Preflight failures
-return `PreSubmitCheckResponse(status="failed", eligible_to_submit=false,
-results=[...])`. Blocked submission-create attempts return
-`DomainError(code="pre_submission_checker_failed")` with structured
-pass/fail/warning details, create no submission row, no submission version, no
-task transition to `submitted`, and no submission-created audit event. They do
-not return review decision values: `accept`, `needs_revision`, or `reject`.
+Blocking pre-submit failures prevent submission creation. The continuous
+submission-bundle preparation request returns
+`DomainError(code="pre_submission_checker_failed",
+details={status, eligible_to_submit, results})` with bounded, path-redacted
+same-request details. It creates no submission row, submission version, task
+transition to `submitted`, or submission-created audit event. There is no
+independent precheck route or standalone pre-submit registry. Results do not
+use review decision values: `accept`, `needs_revision`, or `reject`.
Durable post-submit checker runs execute the complete `execution_checkers` list
from the submission-stamped locked `PostSubmitCheckerPolicy` body. That locked
@@ -323,8 +331,9 @@ Safe evidence references mean opaque Workstream evidence ids, sanitized labels,
- canonical Chunk 8 checker names are registered
- stale Chunk 7 temporary checker names are removed from public docs/templates/tests
- pre-submit feedback executes the task's locked project `PreSubmitCheckerPolicy` and runs without durable checker records
-- preflight failures return `PreSubmitCheckResponse(status="failed", eligible_to_submit=false, results=[...])`
-- blocked submission-create attempts return `DomainError(code="pre_submission_checker_failed")`, include structured pass/fail/warning details, create no submission row, no submission version, no task transition to `submitted`, and no submission-created audit event
+- failed continuous preparation returns `DomainError(code="pre_submission_checker_failed", details={status, eligible_to_submit, results})` with bounded path-redacted same-request details
+- no independent precheck route or standalone pre-submit registry remains
+- blocked preparation creates no submission row, submission version, task transition to `submitted`, or submission-created audit event
- Workstream default submission artifact rules cannot be weakened by project policy
- durable checker runs persist Chunk 8 checker results
- missing required evidence blocks review routing
diff --git a/docs/template_checker_policy.md b/docs/template_checker_policy.md
index 34ce1a2a3..5753b3d71 100644
--- a/docs/template_checker_policy.md
+++ b/docs/template_checker_policy.md
@@ -71,10 +71,10 @@ PreSubmitCheckerPolicy =
trusted compiler output from EffectiveProjectSubmissionArtifactPolicy
```
-Preflight failures return `PreSubmitCheckResponse(status="failed",
-eligible_to_submit=false, results=[...])`. Blocked submission-create attempts
-return `DomainError(code="pre_submission_checker_failed")` with structured
-pass/fail/warning details. Pre-submit failures do not create durable
+Failed continuous submission-bundle preparation returns
+`DomainError(code="pre_submission_checker_failed")` with bounded same-request
+status, eligibility, and pass/fail/warning details. There is no standalone
+preflight route. Pre-submit failures do not create durable
`CheckerRun` records and do not return review decision values: `accept`,
`needs_revision`, or `reject`.
diff --git a/docs/template_submission_artifact_policy.md b/docs/template_submission_artifact_policy.md
index 52f799edb..e4f88f0da 100644
--- a/docs/template_submission_artifact_policy.md
+++ b/docs/template_submission_artifact_policy.md
@@ -82,6 +82,13 @@ override Workstream rules, or weaken default checks.
Every project inherits Workstream default submission artifact rules. Project policy can add stricter requirements, but it cannot remove, weaken, downgrade, or bypass these defaults.
+All defaults are named and versioned in the central Workstream pre-submission
+checker catalogue. The locked project policy adds constrained rules to that
+same catalogue execution; it does not create another API or registry. Catalogue
+availability is deployment-owned. A disabled mandatory entry makes submission
+preparation unavailable, while a disabled advisory entry is explicitly recorded
+and does not silently pass. Project configuration cannot disable either class.
+
Default required packet fields:
- summary
@@ -114,17 +121,19 @@ Default storage rules:
query strings, bucket secrets, and token-bearing references are rejected
before persistence
-Default forbidden artifacts:
+Default high-confidence forbidden artifacts:
- `.env`
- `.git`
-- credentials
-- secrets
-- private keys
-- tokens
+- exact known credential files
+- exact known private-key files
- `.pem`
- `.key`
-- `node_modules`
+
+Broad names such as `token`, `secret`, `credential`, or dependency directories
+are not universal blockers solely because a path contains the word. They must
+be a narrowly defined high-confidence match, an advisory catalogue check, or a
+locked project-specific rule.
A project-required artifact that matches a Workstream default forbidden rule remains blocked. That conflict is a project setup defect.
@@ -212,11 +221,13 @@ Generated policy lock:
Tasks lock this project checker compiled bundle hash before entering the contributor pipeline. Tasks
do not derive or compile their own checker by default.
-Blocked submission-create attempts return `pre_submission_checker_failed` with
-structured pass/fail/warning details.
-The preflight endpoint returns `PreSubmitCheckResponse` with `status`,
-`eligible_to_submit`, and `results`. Neither path returns review decision
-values: `accept`, `needs_revision`, or `reject`.
+Failed submission-bundle preparation returns
+`pre_submission_checker_failed` with bounded same-request status, eligibility,
+and pass/fail/warning details. No independently invocable preflight endpoint or
+ID-addressed evidence-read route exists. These results never use review decision
+values: `accept`, `needs_revision`, or `reject`. After verified preparation,
+final Submission creation consumes the ready admission under fresh authority
+and does not rerun scratch-bound checks.
Expected generated checks:
diff --git a/docs/template_submission_packet.md b/docs/template_submission_packet.md
index c95202671..6a207ae4c 100644
--- a/docs/template_submission_packet.md
+++ b/docs/template_submission_packet.md
@@ -51,13 +51,13 @@ ReviewLease reviewer freeze during contribution creation. Only a prior human
`needs_revision` preparation may have rebased the assignment selector; project
publication or submission input cannot change it.
-Workstream runs pre-submit checks from the locked project pre-submit checker policy before creating the submission.
-Preflight failures return `PreSubmitCheckResponse` with structured
-pass/fail/warning details. Blocked submission-create attempts return
-`pre_submission_checker_failed` with the same structured details, create no
+Workstream runs the single effective pre-submission plan against the uploaded
+outer ZIP in bounded scratch before creating the submission. Failed preparation
+returns `pre_submission_checker_failed` with bounded same-request structured
+details, creates no
submission row, no submission version, and no submission-created audit event,
-and do not return review decision values: `accept`, `needs_revision`, or
-`reject`.
+and does not return review decision values: `accept`, `needs_revision`, or
+`reject`. There is no standalone preflight endpoint.
## Submission Bundle Manifest
@@ -69,13 +69,20 @@ archive permission metadata is excluded. Nested archives remain opaque in v0.1.
## Evidence
-| Type | Label | URI Or Reference | Hash | Proves Which Artifact Or Claim |
-| --- | --- | --- | --- | --- |
-| `Clean path: active guide -> ready task -> finalized submission -> checker pass -> review_pending.
+ Clean path: active guide -> ready task -> verified admission -> immutable submission -> checker pass -> review_pending.
Contributor-fix path: checker failure -> needs_revision -> new submission version.
Setup-defect path: task_setup_blocked -> project manager repair -> trusted checker retry.