Audit public records request timeliness against a statutory deadline

baltor_records_request_timeliness

Audit public records request timeliness against a declared statutory deadline in calendar or working days, with holidays, clock stops and extensions, reporting on-time, late and overdue open requests at an audit date.

Files, names only

LICENSE 1.0 KB
SKILL.md 4.7 KB
contracts/input.schema.json 4.1 KB
contracts/output.schema.json 6.9 KB
examples/example.expected.json 1.9 KB
examples/example.input.json 1.1 KB
references/provenance.json 4.4 KB
scripts/tool.py 13.4 KB
verification/test_tool.py 13.9 KB

Full files in your harness.

What it takes and gives

Command: python3 -B scripts/tool.py < examples/example.input.json
Input fields: audit_date, deadline_rule, weekend_days, holidays, requests
Test: python3 -B -m unittest discover -s verification -p 'test_*.py' -v
Files: SKILL.md, contracts/input.schema.json, contracts/output.schema.json, scripts/tool.py
Placed for: OpenCode

Limits and scope

Limits: This is a supporting calculation for SDG target 16.10 on caller-supplied logs, not a legal determination: whether a clock stop or an extension was lawful, which deadline applies to a request, and how partial responses count are matters for the caller and the applicable law. The tool counts whole dates, not hours, and does not judge the content of responses.

Details

Kind: Skill
Licence: MIT
Declared effects: reads files, runs commands
Placed for: OpenCode
Source: docs/architecture/NORTH-STAR.md
Size: 9 files, 51.4 KB
Identity: baltor_records_request_timeliness
Version: 73391f14d907ded5d1be8536aa4c7e324669c25140c97dbdf97986b25baa5364

The version is the SHA-256 of the item your harness downloads; every file in it names its own checksum.

Where it is shown

Dates, times and time zonesCorner cases

Related components

Something wrong with this item, its rights or its safety? Report it on the support page, or from your harness after a download.