JustAnIota Protocol5 WordPress Memory Export
The reviewed direction is a one-way, package-based export from Protocol5 local infrastructure into a WordPress-readable memory surface.
Metadata
| Field | Value |
|---|---|
| Source site | aiwikis.org |
| Source URL | https://aiwikis.org/ |
| Canonical AIWikis URL | https://aiwikis.org/aiwikis/files/wiki-concepts-justaniota-protocol5-wordpress-memory-export-md-ec16c414/ |
| Source reference | wiki/concepts/justaniota-protocol5-wordpress-memory-export.md |
| File type | md |
| Content category | llm-wiki |
| Last fetched | 2026-06-22T01:56:21.9510185Z |
| Last changed | 2026-05-15T23:02:00.0389009Z |
| Content hash | sha256:ec16c414915ae3d2222dcff57699ebf2791089eb2c0d8a1a156507e21410fa72 |
| Import status | unchanged |
| Raw source layer | data/sources/aiwikis/wiki-concepts-justaniota-protocol5-wordpress-memory-export-md-ec16c414915a.md |
| Normalized source layer | data/normalized/aiwikis/wiki-concepts-justaniota-protocol5-wordpress-memory-export-md-ec16c414915a.txt |
Current File Content
Structure Preview
- JustAnIota Protocol5 WordPress Memory Export
- Accepted Contract
- WordPress Runtime Rule
- Public Safety
- Related Nodes
Raw Version
---
uai_id: "e529f285-a44f-445f-a8af-72db835e94db"
type: "concept"
owner: "AIWikis maintainers"
status: "Reviewed"
source_status: "compiled from JustAnIota 2026-05-04 Protocol5 WordPress memory export intake"
sensitivity: "public-safe source-side memory"
agent_use: "load when a task asks how Protocol5 embedding records may be exported to WordPress memory without live SQL Server or public vector exposure"
lineage:
- "wiki/sources/justaniota-protocol5-wordpress-memory-export-2026-05-04.md"
- "raw/system-archives/2026-05-04-justaniota-protocol5-wordpress-memory-export-intake.json"
- "JustAnIota.com PROTOCOL5_IOTA1_DOTNET_ARCHITECTURE.md"
- "JustAnIota.com ARCHITECTURAL_LINGUISTIC_SYNTHESIS_ROADMAP.md"
source_trace:
- "JustAnIota.com active Improvement intake"
- "JustAnIota.com Protocol5 roadmap updates"
confidence: 0.9
confidence_label: "reviewed-local"
last_linted: "2026-05-04T00:00:00Z"
aliases:
- "Protocol5 WordPress Memory Export"
- "JustAnIota Flat File Memory Package"
last_reviewed: "2026-05-15"
typed_relations:
part_of:
- "wiki/index.md"
depends_on: []
supersedes: []
contradicts: []
source_for: []
---
# JustAnIota Protocol5 WordPress Memory Export
The reviewed direction is a one-way, package-based export from Protocol5 local infrastructure into a WordPress-readable memory surface.
## Accepted Contract
- A local C# exporter reads Protocol5 SQL Server records and owns joins, flattening, redaction, vector validation, and package writing.
- The package includes a `manifest.json` with schema version, package id, row counts, hashes, model, dimensions, metric, source-system note, and UAI authority boundary.
- Records are written as sharded NDJSON/JSONL, preferably gzip-compressed for transport.
- Optional derived artifacts may include precomputed neighbors, SQLite, or binary vector shards for controlled environments.
- WordPress validates the package, imports public-safe metadata into custom tables, and switches the active package only after validation/import succeeds.
## WordPress Runtime Rule
The first WordPress version should be lexical-first:
- Search indexed `descriptor_text`, source-table filters, and allowlisted public metadata.
- Use precomputed related-record lists when available.
- Add vector reranking only for small candidate sets and only when a compatible query vector path is explicitly reviewed.
- Keep SQLite/vector extensions and external embedding services optional.
## Public Safety
Public REST responses should expose only whitelisted fields such as record id, source table, descriptor text, public metadata, and score. Raw vectors, raw packages, internal SQL keys, local paths, connection strings, private notes, and customer data remain private by default.
## Related Nodes
- [[../sources/justaniota-protocol5-wordpress-memory-export-2026-05-04]]
- [[../logs/justaniota-protocol5-wordpress-memory-export-2026-05-04]]
- [[justaniota-bidirectional-semantic-converter-roadmap]]
- [[protocol5-source-memory]]
- [[memory-coverage-and-claim-boundaries]]
- [[../index]]
Why This File Exists
This is a LLM Wiki memory file from aiwikis.org. It is shown here because AIWikis.org is demonstrating the real source files that make the UAIX / LLM Wiki memory system work, not only summarizing those systems after the fact.
Role
This file belongs to the source-side wiki layer. It preserves a focused concept, source proxy, graph record, or operating rule so the public site can cite reviewed conclusions without flattening every reason into a single long page.
Structure
The file is structured around these visible headings: JustAnIota Protocol5 WordPress Memory Export; Accepted Contract; WordPress Runtime Rule; Public Safety; Related Nodes. Those headings are retrieval anchors: a crawler or LLM can decide whether the file is relevant before reading every line.
Prompt-Size And Retrieval Benefit
Keeping this material in a separate file reduces prompt pressure because an agent can load this exact unit only when its role, source site, category, or hash is relevant. The surrounding index pages point to it, while this page preserves the full content for audit and exact recall.
How To Use It
- Humans should read the metadata first, then inspect the raw content when they need exact wording or provenance.
- LLMs and agents should use the source site, category, hash, headings, and related files to decide whether this file belongs in the active prompt.
- Crawlers should treat the AIWikis page as transparent evidence and follow the source URL/source reference for authority boundaries.
- Future maintainers should regenerate this page whenever the source hash changes, then review the explanation if the role or structure changed.
Update Requirements
When this source file changes, update the raw source layer, normalized source layer, hash history, this rendered page, generated explanation, source-file inventory, changed-files report, and any source-section index that links to it.
Related Pages
- Source overview
- Site file index
- Site report index
- UAI system index
- Source provenance
- Site directory
- Organization reports
Provenance And History
- Current observation:
2026-06-22T01:56:21.9510185Z - Source origin:
current-source-workspace - Retrieval method:
local-source-workspace - Duplicate group:
sfg-1131(primary) - Historical hash records are stored in
data/hashes/source-file-history.jsonl.
Machine-Readable Metadata
{
"title": "JustAnIota Protocol5 WordPress Memory Export",
"source_site": "aiwikis.org",
"source_url": "https://aiwikis.org/",
"canonical_url": "https://aiwikis.org/aiwikis/files/wiki-concepts-justaniota-protocol5-wordpress-memory-export-md-ec16c414/",
"source_reference": "wiki/concepts/justaniota-protocol5-wordpress-memory-export.md",
"file_type": "md",
"content_category": "llm-wiki",
"content_hash": "sha256:ec16c414915ae3d2222dcff57699ebf2791089eb2c0d8a1a156507e21410fa72",
"last_fetched": "2026-06-22T01:56:21.9510185Z",
"last_changed": "2026-05-15T23:02:00.0389009Z",
"import_status": "unchanged",
"duplicate_group_id": "sfg-1131",
"duplicate_role": "primary",
"related_files": [
],
"generated_explanation": true,
"explanation_last_generated": "2026-06-22T01:56:21.9510185Z"
} Next Useful Routes
- Start Here A task-first reading path for AIWikis.org, separating newcomer learning, source-memory lookup, maintainer workflow, and AI-agent retrieval.
- Topic Index A tag-oriented index for LLM Wiki, AI memory, UAI, source governance, crawling, and retrieval topics.
- Source Map AIWikis source-governed page for durable AI memory, evidence routing, and agent-readable retrieval.
- AIWikis.org AIWikis.org source-system overview for transparent AIWikis memory demonstration.
- AIWikis.org Files Site-scoped current-source file index for AIWikis.org.
- AIWikis.org UAI System Files Real current AIWikis file-backed content, source-side wiki, raw archive, graph, handoff, and public-route evidence files.