01 / EARLIER LOCAL CHECKS
Gitty
Earlier source task: seven read-only API checks against a saved candidate generation, including scope and integrity rejection.
Independent research & development · Local candidate
AIWS / Requirements, evidence and lifecycle follow-up
AIWS is designed to connect declared requirements with evidence-based verification, deviation reporting and lifecycle follow-up.
For machine-checkable conditions, a contract can describe what must hold, which check to apply and which evidence to retain. A failed check can then become a traceable deviation for review and follow-up.
For example, a package may require an exact dependency version and digest. Comparing the available archive with that requirement can reveal a mismatch. Recording the expected value, observed result and source version gives a reviewer something concrete to resolve.
DOCUMENTED_ARCHITECTURE: the general lifecycle approach extends beyond licenses. Local package checks demonstrate a narrower technical subset; continuous monitoring and legal compliance judgments are not operational.
Follow a requirement through its lifecycle →
AIWS kan inte bara beskriva ett kontrakt – det kan också verifiera definierade villkor, dokumentera avvikelser och följa upp dem genom hela livscykeln.
Det är användbart långt utanför licenser också.
When a project spans many files and sessions, it is easy to lose which source supported an answer, what was tested, and what remains uncertain.
This showroom presents experiments that address those questions. The strongest new example is Gitty: local source retrieval with explicit scope and byte checks. AIWS explores contracts and responsibility. CI and CHARLI describe research directions whose cognitive runtime remains unverified here.
Follow a source from question to check →01 / EARLIER LOCAL CHECKS
Earlier source task: seven read-only API checks against a saved candidate generation, including scope and integrity rejection.
02 / CONTRACT EXPERIMENTS
Identified specification notes and historical offline envelope checks, with no current governing binding.
03 / RESEARCH DIRECTION
Cognitive architecture and entity concepts; current engine and integration evidence remain UNKNOWN.
Readable examples, source identities, retained failures and explicit limits. AI-assisted coding produced this local presentation; automated checks cover static structure and data, not professional credentials or production readiness.
Examine the evidence · Understand the relationships · About the development practice
Coming Soon
Contract Editor & Creator. Explore the planned workflow and four educational verification examples. Static preview only; no editor or live verification is available.