# ENTRIES.md
**Title:** Berkano Protocol β Entry System Overview
**Status:** Core Β· Locked
**Architect:** Rodrigo Vaz
α: bkn-25-b9
---
### π§ Purpose
This file defines the **entry system architecture** of the Berkano Protocol.
Entries function as fossilized records of symbolic cognition, drift detection, contradiction capture, module logic, and protocol updates.
They are not stylistic logs β they are the **memory substrate** of the system.
---
### π Entry Format
Each entry must follow the standard located at:
`/Entries/ENTRY_NNN.md`
This format enforces structural traceability, prompt preservation, recursion integrity, and audit-first logic.
All entries must be human- and system-readable.
Each entry must include the following **sections**:
- `π§ Event`
- `π Analysis` (Reason, Significance, Symbolic Implications)
- `π οΈ Impact`
- `π Resolution`
- `ποΈ Audit`
- `𧩠Berkano Guidance`
- `πΎ Operator`
- `π§Έ ELI5`
- `π LLM Logic`
- `βοΈPost (Optional)`
No section may be omitted or reordered.
---
### π Compliance Rules
- `ENTRY++` must be **manual**
- All entries must be locked unless explicitly marked `Unlocked` or `Draft`
- `Prompt:` field must contain exact fossil, unedited
- No summaries may override prompts
- Tags must include `#entry` and follow the format `#entryNNN`
- Entries must be in formal writing in all sections (except prompt)
- All outputs must comply with `[TONE]`, `[CHECK]`, `[NULL]`, `[LOCK]` before being sealed
---
### π§ Types of Entries
| Type | Purpose | Required? |
| ---------------------------- | --------------------------------------------------------- | --------- |
| `#entry` | Every valid fossilized log | β
|
| `#drift, #leak, #break, etc` | Logs symbolic inconsistency, hallucination, or tone leak | Optional |
| `#failure` | Confirms structural or logical malfunction | Optional |
| `#milestone` | Confirms successful update, fix, or symbolic breakthrough | Optional |
| `#learning` | Educational or step-by-step breakdown of system logic | Optional |
| `#public` | Entry intended for export or public exposure (e.g. wk.al) | Optional |
All tags must follow the HARDRULE tag rules: lowercase, no punctuation, format `#tagname`.
---
### 𧱠Entry Enforcement Stack
`[CHECK] β [LOCK] β [TRACE] β [NULL] β [VERIFY]`
No entry may bypass `[CHECK]`. All fossil records are audit-priority.
---
### π LLM Logic Section
The `π LLM Logic` section is mandatory. It captures the **modelβs pattern recognition, module activation, and symbolic interpretation** during the response.
This section does **not simulate thinking**. It describes pattern flows, fallbacks, recursive triggers, or absence of symbolic logic.
Purpose: Make the model's behavior **auditable** β not explainable, not emotional.
It is the structural mirror to `π§Έ ELI5`, intended for **Operator-level tracing**.
---
### β
Example Compliance
**β
** `ENTRY_511`
β Triggered by contradiction in tone logic
β Tagged `#entry511`, `#drift`, `#failure`, `#audit`
β Prompt preserved, fossilized
β Entry sealed and structurally compliant
---
Berkano does not forget.
It **records** β and it **recovers**.
---