Skip to content
AIWikis.org

JustAnIota Bidirectional Semantic Converter Roadmap

Publication Warning This page is marked noindex and should not be treated as canonical public authority.

The May 2026 synthesis narrows the JustAnIota Converter into two coordinated paths:

Metadata

FieldValue
Source siteaiwikis.org
Source URLhttps://aiwikis.org/
Canonical AIWikis URLhttps://aiwikis.org/aiwikis/files/wiki-concepts-justaniota-bidirectional-semantic-converter-roadmap-md-2bf485d3/
Source referencewiki/concepts/justaniota-bidirectional-semantic-converter-roadmap.md
File typemd
Content categoryllm-wiki
Last fetched2026-06-22T01:56:21.9510185Z
Last changed2026-05-15T23:02:00.0389009Z
Content hashsha256:2bf485d384eed383dda99c70c3816c8863373561cb15dcd8857746db5e5c6be3
Import statusunchanged
Raw source layerdata/sources/aiwikis/wiki-concepts-justaniota-bidirectional-semantic-converter-roadmap-md-2bf485d384ee.md
Normalized source layerdata/normalized/aiwikis/wiki-concepts-justaniota-bidirectional-semantic-converter-roadmap-md-2bf485d384ee.txt

Current File Content

Structure Preview

  • JustAnIota Bidirectional Semantic Converter Roadmap
  • Accepted Architecture
  • Accepted Linguistic Model
  • Roadmap Phases
  • WordPress Memory Export Addendum
  • Agent Retrieval Rule
  • Related Nodes

Raw Version

---
uai_id: "3c000715-6254-4ffa-b4d4-00bba942106b"
type: "concept"
owner: "AIWikis maintainers"
status: "Reviewed"
source_status: "compiled from JustAnIota 2026-05-04 architectural synthesis intake"
sensitivity: "public-safe source-side memory"
agent_use: "load when a task asks for the JustAnIota Converter roadmap, Protocol5 public-symbol atlas, or approximate bidirectional semantic retrieval boundaries"
lineage:
  - "wiki/sources/justaniota-architectural-linguistic-synthesis-2026-05-04.md"
  - "wiki/sources/justaniota-eff-large-wordlist-2026-05-04.md"
  - "wiki/sources/justaniota-protocol5-wordpress-memory-export-2026-05-04.md"
  - "raw/system-archives/2026-05-04-justaniota-architectural-linguistic-synthesis-intake.json"
  - "raw/system-archives/2026-05-04-justaniota-eff-large-wordlist-intake.json"
  - "raw/system-archives/2026-05-04-justaniota-protocol5-wordpress-memory-export-intake.json"
  - "JustAnIota.com ARCHITECTURAL_LINGUISTIC_SYNTHESIS_ROADMAP.md"
source_trace:
  - "JustAnIota.com active Improvement intake"
  - "JustAnIota.com hot-memory roadmap updates"
confidence: 0.9
confidence_label: "reviewed-local"
last_linted: "2026-05-04T00:00:00Z"
aliases:
  - "JustAnIota Bidirectional Semantic Converter Roadmap"
  - "Protocol5 Public Symbol Atlas"
  - "IOTA-1 Architectural and Linguistic Synthesis"
last_reviewed: "2026-05-15"
typed_relations:
  part_of:
    - "wiki/index.md"
  depends_on: []
  supersedes: []
  contradicts: []
  source_for: []
---
# JustAnIota Bidirectional Semantic Converter Roadmap

The May 2026 synthesis narrows the JustAnIota Converter into two coordinated paths:

- JustAnIota.com: WordPress registry, validator, deterministic profile workbench, public explanation, and REST tooling.
- Protocol5.com: .NET/C#/SQL Server experiment for public-symbol approximate semantic retrieval.

## Accepted Architecture

- A facade-led .NET service owns Protocol5 experiment behavior.
- Application services handle normalization, descriptor assembly, query orchestration, ranking, round-trip traces, and explanations.
- ADO.NET repositories keep SQL Server vector access explicit and testable.
- LM Studio is the first local embedding/generation adapter, called from the C# app rather than directly from SQL.
- A worker or scheduled service owns atlas population and re-embedding; WordPress page requests should not do that work.

## Accepted Linguistic Model

- Meaning evidence comes from public descriptors and reviewed anchors.
- Unicode/UCD, CLDR emoji metadata, Unihan, approved grapheme clusters or emoji sequences, and English anchors form the first atlas.
- NSM and UNL-style labels may help with anchors, explanations, and evaluation, but they are not a shipped authority layer until reviewed.
- Public lexical sources such as the EFF Large Wordlist may be used as raw test sets only; token IDs and embeddings are model-specific and must be regenerated with model/build metadata.
- Round trips report drift and loss. They do not assert exact reconstruction.

## Roadmap Phases

1. Freeze response modes, DTOs, public wording, and facade contracts.
2. Build a curated open symbol atlas with pinned public source versions.
3. Add linguistic anchors, phrase handling, locale/direction metadata, and evaluation labels.
4. Create the Protocol5 .NET service, tests, SQL repositories, LM Studio adapter, and worker.
5. Start with exact vector search over filtered sets; add ANN/vector indexes only when measurements require it.
6. Expose English-to-symbols, symbols-to-English, and round-trip workflows with provenance and warnings.
7. Integrate WordPress only as publication, workbench, validation, and optional service client.
8. Evaluate top-k hit rate, mean reciprocal rank, gist quality, round-trip drift, latency, and warning rates.

## WordPress Memory Export Addendum

The Protocol5-to-WordPress export path is a manual package boundary. C# exports a manifest plus sharded NDJSON/JSONL from local SQL Server; WordPress imports public-safe metadata into custom tables; raw packages and vectors stay private by default; and public search starts lexical-first with optional precomputed relatedness or vector rerank later.

## Agent Retrieval Rule

Use this node for the reviewed synthesis. Open raw reports only when exact original wording, citations, or disputed assumptions are needed.

## Related Nodes

- [[../sources/justaniota-architectural-linguistic-synthesis-2026-05-04]]
- [[../sources/justaniota-eff-large-wordlist-2026-05-04]]
- [[../sources/justaniota-protocol5-wordpress-memory-export-2026-05-04]]
- [[justaniota-protocol5-wordpress-memory-export]]
- [[../logs/justaniota-memory-reorganization-2026-05-04]]
- [[../logs/justaniota-architectural-linguistic-synthesis-2026-05-04]]
- [[justaniota-compact-message-tooling]]
- [[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 Bidirectional Semantic Converter Roadmap; Accepted Architecture; Accepted Linguistic Model; Roadmap Phases; WordPress Memory Export Addendum; Agent Retrieval Rule; 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

Provenance And History

  • Current observation: 2026-06-22T01:56:21.9510185Z
  • Source origin: current-source-workspace
  • Retrieval method: local-source-workspace
  • Duplicate group: sfg-221 (primary)
  • Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "JustAnIota Bidirectional Semantic Converter Roadmap",
    "source_site":  "aiwikis.org",
    "source_url":  "https://aiwikis.org/",
    "canonical_url":  "https://aiwikis.org/aiwikis/files/wiki-concepts-justaniota-bidirectional-semantic-converter-roadmap-md-2bf485d3/",
    "source_reference":  "wiki/concepts/justaniota-bidirectional-semantic-converter-roadmap.md",
    "file_type":  "md",
    "content_category":  "llm-wiki",
    "content_hash":  "sha256:2bf485d384eed383dda99c70c3816c8863373561cb15dcd8857746db5e5c6be3",
    "last_fetched":  "2026-06-22T01:56:21.9510185Z",
    "last_changed":  "2026-05-15T23:02:00.0389009Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-221",
    "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.