AIWS showroom

Independent research & development · Local candidate

Contract Editor & Creator / Coming Soon

AIWS Contract Studio

Make rules and evidence easier to understand

PLANNED: future authoring features could show each requirement beside its verification rule, required evidence and possible deviations. A reader could see why a check matters and what a later review would need.

For example, a dependency rule could explain the required version and digest, the archive used as evidence, and why a mismatch needs correction. A future comparison view could connect a retained failure to a later candidate and recheck result.

This is a static explanation. No authoring tool, automated deviation tracker or lifecycle follow-up service operates here. The existing educational examples remain conceptual; package CLI checks are separate from this planned interface.

Read the lifecycle model · Understand the bounded package checks

Coming Soon · Planned capabilities

Understand the contract before it guides the work.

Contract Editor & Creator is a planned AIWS workspace for making contract structure, rules and evidence easier to inspect. This showroom presents the idea through static educational examples.

No editor, importer, validator, API connector or runtime integration exists in this showroom. Nothing on this page executes verification, imports files or grants authority.

01 / Start with a template02 / Understand the rules03 / Review a candidate

A clearer path from example to candidate.

PLAN / CREATE

Templates with context

Create contracts from templates. Import supported test examples, understand each test’s expected outcome and create new candidate contracts from examples.

PLAN / EDIT

Guidance and precise control

Edit contracts in guided and raw modes. Explain rules in understandable language while keeping the underlying structure inspectable.

PLAN / INSPECT

See what a change affects

Inspect relationships and dependencies, compare contract versions and differences, and validate contract structure against applicable schemas when available.

All capabilities above are planned. Schema availability and supported import formats remain UNKNOWN. Structural validation would not prove authorization, semantic correctness or runtime safety.

Four rules worth understanding.

Read the conditions, then the limits. These are static illustrations, not original Gitty tests or a Gitty regression suite. No live verification occurs. Expected outcomes below are conceptual, not measured results.

Source basis: documented verification principles in the inherited Gitty evidence and standalone demonstration. Earlier Gitty API observations remain separate from standalone synthetic examples. Neither is rerun by this page.

01 / Conceptual illustration · no execution

Gitty source integrity check

Expected condition: returned bytes match an explicitly pinned source digest.

What & why
Check source byte identity so a retrieval result cannot silently substitute different content.
Relevant input
Identified source bytes, their expected digest and the selected generation pin. No original bytes or private digests are shown.
Expected success
Matching bytes support identity relative to that pin.
Expected failure
A mismatch requires integrity rejection; do not use the result as verified source.
Cannot prove
Truth, trusted authorship, currentness, distribution rights or an authorized pin.
Evidence label
Conceptual illustration based on historical source records. Earlier API observations recorded VERIFIED and INTEGRITY_FAILURE; not locally rerun for this preview.

02 / Conceptual illustration · no execution

Gitty project-scope rejection

Expected condition: request project and scope match the selected route.

What & why
Check project isolation so nearby sources do not become members of another project by accident.
Relevant input
Requested project and scope, plus the explicitly selected route’s project and scope declarations.
Expected success
A match permits only the next scoped check; it does not establish overall verification.
Expected rejection
A wrong project or scope must be rejected rather than silently searched elsewhere.
Cannot prove
A valid authority grant, complete access control, ownership or safe execution.
Evidence label
Conceptual illustration based on historical source records. Earlier API observations recorded SCOPE_REJECTED; not locally rerun for this preview.

03 / Conceptual illustration · synthetic basis

CSV and SQLite agreement

Expected condition: portable records agree with the selected searchable projection.

What & why
Compare relevant CSV and SQLite records to detect a stale or inconsistent projection. An index is not authority.
Relevant input
A selected CSV record, corresponding SQLite record and declared source identity within one fixture or generation.
Expected success
Agreement supports consistency for the compared records only.
Expected failure
A missing or different record prevents a verified agreement claim.
Cannot prove
Whole-dataset completeness, original source truth, an atomic snapshot or Gitty regression correctness.
Evidence label
Conceptual illustration based on the inherited standalone synthetic demonstration and documented query principles. The demonstration is not a Gitty test; no database is opened by this page.

04 / Conceptual illustration · no execution

Receipt/Handover hash linkage

Expected condition: the Handover references the digest of the exact Receipt bytes.

What & why
Check that continuity documents refer to the intended version rather than an accidentally replaced Receipt.
Relevant input
Receipt bytes, their computed digest and the Receipt digest recorded by the Handover.
Expected success
A match supports byte linkage between those two records.
Expected failure
A missing or mismatched reference leaves continuity unverified and needs investigation.
Cannot prove
Authenticated identity, independent verification, approval, correctness of the Receipt’s claims or a new grant.
Evidence label
Conceptual illustration based on historical linkage records and an inherited synthetic linkage test. No private Receipt, identity or digest is displayed.

A candidate stays a candidate.

AIWS describes semantics and contract boundaries. Contract Studio is a planned authoring interface; this preview establishes no IMPLEMENTS, INTEROPERATES_WITH or active governing relationship. A template, example, successful check or saved candidate cannot automatically promote authority.

Review and authorization remain separate decisions. Publication and kit distribution remain BLOCKED. License and distribution rights remain unresolved. The standalone demonstration is not a Gitty regression test. Windows verification remains NOT_TESTED.

Explore AIWS · Inspect project relationships · Read Windows/Linux dependencies and release restrictions

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.