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.
Independent research & development · Local candidate
Contract Editor & Creator / Coming Soon
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.
PLAN / CREATE
Create contracts from templates. Import supported test examples, understand each test’s expected outcome and create new candidate contracts from examples.
PLAN / EDIT
Edit contracts in guided and raw modes. Explain rules in understandable language while keeping the underlying structure inspectable.
PLAN / INSPECT
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.
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
Expected condition: returned bytes match an explicitly pinned source digest.
02 / Conceptual illustration · no execution
Expected condition: request project and scope match the selected route.
03 / Conceptual illustration · synthetic basis
Expected condition: portable records agree with the selected searchable projection.
04 / Conceptual illustration · no execution
Expected condition: the Handover references the digest of the exact Receipt bytes.
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
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.