AIWS showroom

Independent research & development · Local candidate

Verification kits / Local candidates; publication not authorized

Inspect the requirements first.

How package contracts support lifecycle checks

A package contract declares identity, version and project scope. A dependency lock adds the exact required archive digest. License metadata links source evidence and records unresolved rights explicitly. Together, these give the offline verifier concrete values to compare.

Example: if a standalone kit requires a particular Contract Core archive, a different digest fails the dependency check even if the filename looks right. The failed result can be retained with its expected pin; a corrected candidate can be checked again without erasing the earlier failure.

IMPLEMENTED_AND_LOCALLY_TESTED: bounded local integrity, dependency and metadata checks. DOCUMENTED_ARCHITECTURE: using those results in a broader deviation and follow-up process. No continuous compliance service or legal judgment is operational.

Package details are available below. ZIP release awaits authorization.

Future AIWS License capability — local technical candidate

Private technical review only. Public redistribution is not authorized.

Licensing evidence and verification limits

License extension 0.1.0 in package candidates 0.2.0 checks source byte linkage and metadata consistency. Legal status: RIGHTS_HOLDER=UNKNOWN; LEGAL_BASIS=UNDECIDED; legal terms EVIDENCE_MISSING; DISTRIBUTION_GRANT=NOT_GRANTED; distribution BLOCKED; SIGNATURE_STATUS=UNSIGNED; AUTHORITY=NONE. Technical PASS grants no legal rights or runtime permission. Future legal clearance, authenticated signatures and trusted timestamps remain unimplemented and UNVERIFIED. BYTE_MATCH proves identical bytes, not ownership. No public ZIP download is available.

Contract-bound package architecture

AIWS Contract Core candidate → exact pinned dependency → Standalone Verification Kit candidate → future Contract Studio examples.

The Contract Core is a proposed, non-governing reusable format and verifier. The kit reuses an independent synthetic retrieval demonstrator and does not test original Gitty. Integrity-only verification works without the core; integration preflight requires its exact archive bytes. No substitution, installation, fetching or operational Registry exists.

Generated contract package metadata. Linux tests were executed locally; Windows remains NOT_TESTED. Same-performer checks do not establish independent verification. Rights remain unresolved.

Assets (2)

Public ZIP release awaits ownership, licensing and distribution authorization. SHA-256 verifies bytes, not distribution rights. Release evidence and limits.

aiws.contract-core-0.2.0.zip69,084 bytesRelease pending authorization
Details for aiws.contract-core

AIWS Contract Core candidate. Version 0.2.0. Contract format 1.0.0; scope aiws.contract-core.candidate.

SHA-256
1741412cd68fd4594d57938e949b1da2d79036715e2781b425591565a9287b49
Required packages (exact)
None (no required package dependencies).
Runtime
CPython >=3.10; standard library; SQLite for synthetic kit tests only
Windows
NOT_TESTED
aiws.standalone-verification-0.2.0.zip78,353 bytesRelease pending authorization
Details for aiws.standalone-verification

Standalone Verification Kit candidate. Version 0.2.0. Contract format 1.0.0; scope synthetic.retrieval.only.

SHA-256
98a7c20a0ad5a35939a225afa1a3cc453eb63a302df9f0466c4a3a92d0633a7c
Required packages (exact)
aiws.contract-core 0.2.0; scope aiws.contract-core.candidate; SHA-256 1741412cd68fd4594d57938e949b1da2d79036715e2781b425591565a9287b49
Runtime
CPython >=3.10; standard library; SQLite for synthetic kit tests only
Windows
NOT_TESTED

Gitty Verification Kit — release blocked

The original Gitty sources are private read-only references. No redistribution license or explicit distribution grant was established. No original Gitty ZIP has been produced and no download link is offered.

Historical original test results, current read-only API observations, standalone reproducer tests and full-product tests have separate scopes. The standalone material below cannot substantiate a full Gitty claim. Full-product tests were not run.

Review Gitty evidence and retained limitations · Machine-readable requirements

The historical 0.1.0 synthetic retrieval demonstrator is retained as evidence; it is not an additional download.

Execution instructions are not test evidence

Local workspace material includes README.md, README-WINDOWS.md, README-LINUX.md, DEPENDENCIES.md, requirements.json, source/fixture notes, integrity checks and runnable tests. It is withheld from distribution pending rights review.

Linux: CPython 3.10 or newer with sqlite3; run sh run-tests.sh. Windows design: CPython 3.10 or newer with sqlite3 and Python Launcher; run run-tests.bat, which pauses and preserves the exit code. WINDOWS_EXECUTION=NOT_TESTED. No installation, network or administrator access is requested.

Observed local outcomes are recorded separately in the task TEST-RESULTS.md. No independent verifier participated. Identity UNSIGNED.