Observed here
Retrieve and check
Seven read-only API checks produced their expected statuses against one saved candidate generation. Returned source bytes matched the original.
Independent research & development · Local candidate
Gitty / Source continuity and verified retrieval
Verification kits: requirements, scope and distribution blockers
Gitty addresses a common development problem: an answer survives, but the source version, project context and failed checks disappear.
Within the inspected candidates, Gitty is a local source-indexing and verified-retrieval implementation. It connects readable search records to structured records and original source bytes. It helps answer “which source supports this?” rather than treating a search hit as accepted knowledge.
Observed here
Seven read-only API checks produced their expected statuses against one saved candidate generation. Returned source bytes matched the original.
Recorded earlier
REVIEW-001 integration records 105 unittest executions across seven unittest suites, plus one CLI assertion script: eight selected suites in total.
Still unresolved
CE2 remains OPEN. PRODUCT_ROOT, current project authority and authenticated independent verification remain UNKNOWN or unestablished.
CSV exposes the portable search projection: a reviewer can inspect search text, scope and record locators without treating an opaque database as the only source of context. In the inspected query code, CSV is searched first. Matching record IDs then select corresponding SQLite records, whose scope and source references are checked.
SQLite contributes structured lookup and consistency checks. It is a rebuildable projection in this information model; it does not replace the original source or decide authority. The showroom’s downloadable CSVs are a separate presentation projection, not Gitty’s Registry or authoritative project database.
SHA-256 checks whether bytes match an expected digest. A different digest rejects the proposed byte identity. Matching bytes alone cannot establish truth, safe behavior, authorship, ownership or permission. A pin supplied by the same untrusted party needs a separately justified trust anchor.
Receipt identifies delivered artifacts and checks. Handover links the receipt and preserves the frontier, blockers and continuation context. Here their hash links match; their identities remain UNSIGNED.
Observed API readback + conceptual routing context · not one end-to-end Registry execution
Question: “Find the policy-loader source in the Gitty candidate so it can be reviewed.” Sources G-CONSUMER, G-READBACK and G-QUERY support the steps below.
Conceptual diagram · source-grounded mechanism
Question → explicit project → verified route or explicit pinned generation → project CSV → matching SQLite records → original-byte check → scoped answer / explicit failure
The inspected broader query function permits parent/Master fallback only after a verified project miss, with a verified edge and the specified fallback policy, where the relevant contract permits it. An unreadable, stale or corrupt index is not a verified miss. The saved generation explicitly marks fallback DISABLED and edge verification UNKNOWN. The observed Consumer API does not discover routes or perform this fallback. Master remains REFERENCE_ONLY; a reference never transfers project ownership.
| Outcome | Meaning in this candidate | What follows |
|---|---|---|
| FOUND / VERIFIED | A scoped hit or successful integrity check | Review identified evidence; no authority gained |
| NOT_INDEXED | No match in the available verified projection | Do not infer the source does not exist elsewhere |
| INTEGRITY_FAILURE | Generation, pin or source verification failed | Stop; do not turn index failure into a search miss |
| SCOPE_REJECTED | Explicit project/scope does not match | Stop; do not silently search another project |
Linked identities below resolve to sanitized summaries, not private source payloads. Exact paths, versions and SHA-256 values remain in task-local evidence, outside dist/.
| Precise claim / source identity | Reported outcome | Verification level here | Limit |
|---|---|---|---|
| G-INTEGRATION: REVIEW-001 integration | 105 unittest executions; 8/8 selected suites exit 0; 176 ZIP entries | Original reports/logs inspected; 175 manifest entries matched; Handover link matched; ZIP counted | Historical tests not rerun. Full regression not run; inherited 9 failures and 1 error unresolved |
| G-CONSUMER: read-only consumer | 19 consumer, 7 realfile and 86 policy checks reported separately; real-source CLI PASS | 30 manifest entries and Receipt linkage matched; implementation inspected | Counts include inherited/imported tests; historical generation and custody limitations persist |
| G-REVIEW: earlier source consumption | PASS_WITH_REVIEW_FINDING; malformed owner list raised TypeError | 24 manifest entries matched; report inspected | Stubbed dependency probe; no demonstrated trust bypass. Later correction is a distinct version |
| G-READBACK: this task’s saved-generation API checks | 7 expected statuses; decoded original-byte equality | Locally re-executed and byte-checked by the performer | One candidate generation; no independent verifier, production test or full regression |
| G-QUERY: CSV-first query mechanism | Code implements route checks, CSV selection, SQLite agreement and conditional fallback | Original implementation bytes inspected and manifest-matched | Mechanism observation; operational Registry and fallback were not executed here |
| G-REFRESH: original-source generation | 86 policy and 7 realfile checks reported separately | 55 manifest entries matched; source chain followed | Historical failures retained; atomic multi-file snapshot and privileged ABA guarantees unproven |
Independent verification: NOT_PERFORMED. A recorded result, a terminal readback, locally reverified bytes and independently verified behavior are different evidence levels. This task establishes the middle two only within its stated scope.
Observation: the inspected code separates lookup, structured record checks and original-byte verification. Interpretation: that separation helps locate failures instead of accepting every search result. Hypothesis: it could improve continuity across larger workflows; broader evaluation is needed.
What could limit the claim? Missing source bytes, untrusted pins, stale projections, inconsistent records or an unauthorized route can prevent a supported answer. Passing selected tests does not remove custody, concurrency or deployment questions.
Gitty concerns source continuity. AIWS concerns semantics and contract boundaries; CI concerns cognitive architecture; CHARLI concerns a distinct entity. Harbour and NodeFlow retain their own execution/control and coordination scopes. No live integration, project membership or governing binding among these projects is established by this page. Inspect the typed relationships.