Public architecture
Technical documentation
Public technical principles for evidence integrity, provenance, explainability, uncertainty, and accountable human review.
This documentation explains the public contracts that shape AnankeNet. It is intended for engineers, researchers, reviewers, security practitioners, and technical decision-makers.
It deliberately describes properties and boundaries, not sensitive operational implementation. Exact detection logic, indicators, thresholds, weights, platform-specific behavior, internal prompts, operational datasets, evidence, and investigative leads are outside the publication boundary.
How to read these documents
The sequence begins with the information layers, then follows the preserved source through integrity, provenance, analysis, and human review. The final document explains the public security boundary.
These pages describe a research architecture. They do not claim operational deployment, real-world performance, or external approval.
The strict separation between preserved material, extracted facts, calculations, interpretation, hypotheses, and human judgment.
Why original material is preserved before transformation and how later changes should remain detectable.
How important records remain traceable to their sources, transformations, versions, and accountable actions.
Public requirements for explainable analytical output, contextual interpretation, and visible uncertainty.
The records needed to understand and, where practical, reproduce an analytical result later.
What an accountable reviewer needs to inspect, question, correct, and decide without being reduced to an approval click.
What this public documentation can explain and what remains private for security, privacy, and evidence protection.