OBLITERATUS/WORKSPACE.md

WORKSPACE.md

AIWG Context Graph

This file is the canonical provider-neutral home for project and operator context. Provider startup files are generated adapters: they direct the harness here first, then to AIWG.md for framework discovery and routing.

Precedence

1. Provider, system, and organization instructions retain their native authority.
2. Root WORKSPACE.md supplies shared project/operator context.
3. AIWG.md supplies generated framework/discovery context.
4. Narrower linked files and provider-native subtree instructions govern their declared scope.

Ownership

• Edit project-neutral notes only inside the protected Project Context section below.
• Keep detailed policies, runbooks, hooks, and quickrefs in linked files.
• Keep provider-only directives in .aiwg/context/providers/.
• Never store secrets, tokens, credentials, or machine-local sensitive values here.

Linked Context

• AIWG framework context
• AIWG project configuration
• Project-local quickref (when configured)

Project Context

OBLITERATUS is a Python research tool. The default pull-request baseline must be CPU-safe, deterministic, and must not download models or require network, accelerator, or remote-execution credentials.

Canonical required checks:

• python -m ruff check --select F app.py obliteratus tests scripts/check_coverage_thresholds.py scripts/check_supply_chain_policy.py scripts/gemma4_12b_recursive_loop.py
• python -m pytest (includes the measured 49% coverage floor)
• CI additionally enforces the measured 36% branch-coverage floor from its retained coverage JSON report.
• python -m build --sdist --wheel
• python -c 'import obliteratus; print(obliteratus.__version__)'
• python -m obliteratus --help

CI additionally validates wheel and sdist metadata, installs each distribution in an independent environment outside the checkout, exercises both CLI entry paths, and retains the distributions plus evidence. Immutable CI action/tool pins are recorded in ci/digests.txt.

Python CI resolution is locked by uv.lock, including the official CPU-only PyTorch source for Linux and Windows. The required Supply chain job scans all supported Python versions for known vulnerabilities, scans the checkout for secrets with fully redacted evidence, enforces the packaged-dependency license allow list, and binds a CycloneDX SBOM to the built wheel. Exception and update rules are documented in docs/SUPPLY_CHAIN_POLICY.md.

GPU, MPS, model-download, network, and remote-execution checks are conditional release or risk-surface gates, not part of the default CPU job.

Use .aiwg/bt6-maintainer.yaml and the project-local bt6-maintainer bundle for issue, pull-request, provider, and merge-train work. Maintainers may add missing tests to already-reviewed legacy pull requests as a one-time transition courtesy. New changes must include relevant tests and keep the complete required suite green.