Bedrock done-claim checker: a small harness around one model
Send a claim that some work is done plus the evidence for it; get back supported, partial,
unsupported or unparseable. The point is the harness, not the model:
| Harness part | Where |
|---|---|
| Daily call cap checked before Bedrock is called (DynamoDB counter, 429 past the cap) | src/handler.py take_budget |
| Size limits on input, fixed max output tokens | MAX_CLAIM, MAX_EVIDENCE, MAX_TOKENS |
| Deterministic checks first: no evidence, no concrete artifact, claim terms missing from evidence | deterministic_checks |
| One model, chosen at deploy time; no routing between models | ModelId parameter |
Model output accepted only in the exact JSON shape; anything else is unparseable |
parse_model_reply |
A "supported" from the model is downgraded to partial when the checks flagged something |
check |
Concurrency pinnable (ReservedConcurrency, off by default: new AWS accounts allow only 10 concurrent executions and keep all 10 unreserved); IAM role can invoke exactly one model |
bedrock-harness-demo.yaml |
| Function URL private (IAM auth) by default | UrlAuthType |
Flow
flowchart LR
C["Caller<br/>claim + evidence"] --> U["Function URL<br/>IAM auth (private)"]
U --> L["Lambda<br/>concurrency pinnable"]
L --> D{"Deterministic checks<br/>evidence? artifacts?<br/>claim terms covered?"}
D -->|no evidence| X["unsupported<br/>model never called"]
D --> B{"Daily cap<br/>DynamoDB counter"}
B -->|cap reached| R["429<br/>model never called"]
B --> M["Bedrock<br/>one model, set at deploy"]
M --> P{"Exact JSON shape?"}
P -->|no| N["unparseable"]
P -->|yes| V["verdict<br/>downgraded if checks flagged"]
Run
./preflight.sh # one tiny call: can this account reach the model at all?
./deploy.sh # stack + code upload (private URL)
./invoke.sh # one weak claim, one strong claim
./teardown.sh # delete everything and prove it is gone
Defaults: us-east-1, amazon.nova-micro-v1:0, 100 model calls per day.
Install as a library (pending the first release)
Not on PyPI yet. This becomes available after the first release (
v0.1.0):
pip install bedrock-done-claim-checker
The package is the handler only: from bedrock_done_claim_checker.handler import check, deterministic_checks.
Standard library only; lambda_handler also needs boto3. The scripts above are not in the package; run them from a clone.
Status
First live run 2026-10-27 (us-east-1, amazon.nova-micro-v1:0, private IAM-auth URL; run from CloudShell, no access keys):
| Check | Result |
|---|---|
| Unsigned request to the function URL | 403 |
| Weak claim (no artifacts in evidence) | unsupported |
| Strong claim (hash, test output, timestamp) | partial on the first run, then supported after a fix (below) |
| Daily counter after the run | 5, matching the 5 model calls made |
What the live run found, both fixed:
- New AWS accounts can't pin Lambda concurrency. Their total limit is 10, and Lambda keeps all 10 unreserved, so
ReservedConcurrentExecutions: 1failed the stack. Pinning is now an opt-in parameter (ReservedConcurrency, default 0); the daily cap still bounds spend. - The deterministic word check was too literal. It flagged "deployed" and "tests" as missing from evidence that said "deploy" and "pytest", and downgraded a claim the model had right. Claim words are now stemmed, with a regression test.
Offline: cfn-lint clean, 11 unit tests pass (python3 -m unittest discover -s tests). This is a small two-claim smoke test, not an accuracy benchmark.
Independent project by CloudLab Works; not affiliated with or endorsed by AWS.
MIT licensed.
Metadata
Release files for bedrock-done-claim-checker 0.1.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 |
|---|---|---|---|---|
| bedrock_done_claim_checker-0.1.0.tar.gz | 16.6 kB | With provenance | Details for bedrock_done_claim_checker-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| bedrock_done_claim_checker-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for bedrock_done_claim_checker-0.1.0-py3-none-any.whl |
Total release size: 24.1 kB
Release files / bedrock_done_claim_checker-0.1.0.tar.gz
| Download URL | bedrock_done_claim_checker-0.1.0.tar.gz |
|---|---|
| Size | 16.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9e6692918e0c2b2552588467cad7863447eaf5c3432a4e4a52a99ec87cf72cb6
|
|
BLAKE2b-256 checksum How to use checksums |
144acdcb2b525d427f293f874987e24dab4e5c5ad8ae7ee263a70b8e6b5ef8ba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 11, 2026.
Transparency logRelease files / bedrock_done_claim_checker-0.1.0-py3-none-any.whl
| Download URL | bedrock_done_claim_checker-0.1.0-py3-none-any.whl |
|---|---|
| Size | 7.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
461c41f76738050263b1a70a893dec3054d90ce98fc2674937f3986f98d05115
|
|
BLAKE2b-256 checksum How to use checksums |
8c4ab5f88612c7f57145458b61bf3000db62897fc0fa50a77c554e2108b274b2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 11, 2026.
Transparency logSecurity for bedrock-done-claim-checker 0.1.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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for bedrock_done_claim_checker-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 11, 2026.
Transparency logA 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.