# PHIROK

> PHIROK by KRONS Systems is a platform for verifiable memory and persistent evidence for AI systems.

PHIROK records evidence and context, with cryptographic receipts, append-only history, tenant-scoped separation, non-generative GraphRAG retrieval and deterministic reconstruction of stored memory state.

## Read the site

- [PHIROK — Verifiable memory for AI in production](https://phirok-evidence.lferro.chatgpt.site/): Verifiable memory and persistent evidence for AI systems. Explore cryptographic receipts, tenant-scoped records and deterministic replay.
- [Platform — PHIROK](https://phirok-evidence.lferro.chatgpt.site/platform/): Explore evidence-first history, cryptographic receipts, append-only records, tenant separation, traceable retrieval and replay.
- [Architecture — PHIROK](https://phirok-evidence.lferro.chatgpt.site/architecture/): Follow authenticated evidence capture into append-only storage, cryptographic lineage, retrieval and review.
- [Trust model — PHIROK](https://phirok-evidence.lferro.chatgpt.site/trust/): Understand the boundaries of integrity, provenance, tenant isolation and replay. Clear mechanisms and explicit limits.
- [Evidence playground — PHIROK](https://phirok-evidence.lferro.chatgpt.site/playground/): Compare sample decision records and test a local cryptographic integrity check. Inspect evidence and understand what a hash can prove.
- [Developers — PHIROK](https://phirok-evidence.lferro.chatgpt.site/developers/): Read the PHIROK evidence model, integration boundaries and evaluation criteria. Plain HTML and Markdown for people and agents.
- [Evaluate PHIROK — Get started](https://phirok-evidence.lferro.chatgpt.site/access/): Prepare an evaluation brief for a consequential AI workflow, or continue to the PHIROK application for account access.
- [Site privacy — PHIROK](https://phirok-evidence.lferro.chatgpt.site/privacy/): How the PHIROK website handles local preferences, demonstration input, downloads and links to its application.

## Boundaries

- A receipt does not make a source factually true.
- Replay concerns retained memory state, not a guarantee of identical model generations or access to hidden reasoning.
- The current semantic layer uses deterministic test fixtures. Commercial production embeddings are not advertised.
- No mathematical hallucination prevention, live contradiction detection or regulatory certification is claimed.
- Interactive examples on this site are illustrative. The local SHA-256 example is not PHIROK's production BLAKE3 receipt implementation.
- This site does not publish an API endpoint or a versioned API request contract. Obtain deployment-specific documentation before integrating.

## Technical brief

- [Full plain-text overview](https://phirok-evidence.lferro.chatgpt.site/llms-full.txt)

## Evidence model

A record connects source material, retrieved context and configuration, policy references, and an authoritative receipt reference. Production frontend code must not invent receipt identifiers or verification facts.

## Persistence and integrity

PHIROK's described core uses append-only WAL storage and BLAKE3 hashes. Cryptographic lineage makes changes detectable against a trusted reference. Trusted checkpoints, retention and operational recovery remain necessary; hashing alone does not prevent all data loss or infrastructure failures.

## Tenant boundaries

Tenant scope comes from authenticated backend context and must be enforced on reads and writes. A tenant field in a payload is not proof of authorization. The access model includes centralized authentication, email verification by link, JWT sessions and protected MCP/gRPC boundaries designed to fail closed.

## Retrieval and replay

Non-generative GraphRAG returns evidence and relationships rather than generating an answer. Deterministic replay reconstructs retained memory state. It does not establish a model's private reasoning or guarantee identical future model output. Background maintenance supports the memory operations.

## Evaluation criteria

1. Retain evidence, receive an authoritative receipt and resolve it to the retained record.
2. Retrieve evidence and inspect its provenance.
3. Restart the deployment and verify retained-state recovery.
4. Confirm that authenticated tenant A cannot access tenant B's evidence.
5. Inspect explicit failures for invalid input, unavailable storage and unauthorized access.

## Site examples

The comparison contains three fixed, illustrative records. The integrity example hashes exact UTF-8 text using browser-native SHA-256 and compares it to a reference held in the current page. It is not a signature, a trusted timestamp or production receipt. Editing both data and reference defeats that local example. Site inputs are not sent to a PHIROK backend; exports are created locally.