Reference
Output Locations
Where generated modules land, and how module/API staleness is tracked.
For a spec module my_app.specs (under src/), Jaunt writes:
- Generated implementation:
src/my_app/__generated__/specs.py - Generated import path:
my_app.__generated__.specs
For a test spec module tests.specs_email (under project root), Jaunt writes:
- Generated tests:
tests/__generated__/specs_email.py - Generated import path:
tests.__generated__.specs_email
Generated files include a header like:
# This file was generated by jaunt. DO NOT EDIT.
# jaunt:kind=build|test
# jaunt:source_module=...
# jaunt:generation_fingerprint=sha256:...
# jaunt:module_api_digest=sha256:...
# jaunt:module_context_digest=sha256:...
# jaunt:module_digest=sha256:...Jaunt uses these header digests to decide whether a module is stale and needs regeneration.
module_digest covers the module's own spec inputs. module_api_digest covers the exported dependency contract seen by downstream modules: callable signatures, the full cleaned docstring contract, and for whole-class specs, declared members and method signatures.
That means an upstream API change can make downstream modules stale even when the downstream source file itself has not changed.
Next: OpenAI Backend.