TR-CORE-API-LIMITS / Teal / Review draft

API process and resource boundaries

Terminology revised · September 12 evidence

Later individual Teal rerun. The reported execution status is historical and is not a new test result.

TEAL LIBRARY RERUN  |  12 SEPTEMBER 2026  |  Michael Patrick Bangel
18
TEAL-RERUN-03-B001 | RELATED_EXECUTION_EVIDENCE_AVAILABLE
TR-CORE-API-LIMITS / API process and resource boundaries
IF
A service request declares limits or cancellation.
HOW
Allow only bounded attenuation of defaults; distinguish the trusted in-process facade from the isolated/stdio
host that enforces wall time and process handling.
THEN
Report cancellation or resource refusal explicitly. In-process fixture success does not establish hostile-host
isolation.
CURRENT EVIDENCE
Fresh related language/paper/water checks are in the evidence ledger. The test count is suite evidence, not
proof of every branch in this requirement.
REMAINING REQUIREMENT
Use the source and recorded case evidence to close remaining per-branch, native-host and full-contract coverage gaps.
SOURCE REFERENCES
bangel:language/python/src/bangel/api.py; bangel:language/python/src/bangel/client.py; associated-core:reference/src/bangel/api.py;
associated-core:reference/src/bangel/client.py; associated-core:products/water/legacy/hagar-python/src/mjos_hagar/api.py

Publication is pending owner review. White papers are excluded.