Progress

uai: 1.0 type: progress project: Protocol5 updated: 2026-05-08

Metadata

Field	Value
Source site	protocol5.com
Source URL	https://protocol5.com/
Canonical AIWikis URL	https://aiwikis.org/protocol5/files/uai-progress-uai-9368034c/
Source reference	.uai/progress.uai
File type	uai
Content category	uai-system
Last fetched	2026-06-22T01:56:21.9510185Z
Last changed	2026-05-16T01:58:54.1536696Z
Content hash	sha256:9368034c751b8fb23f3fa72fdec67022137a95bb4d10ac77c4fb2a9a7840a3af
Import status	unchanged
Raw source layer	data/sources/protocol5/uai-progress-uai-9368034c751b.uai
Normalized source layer	data/normalized/protocol5/uai-progress-uai-9368034c751b.txt

Current File Content

Structure Preview

• No Markdown headings were detected in this file.

Raw Version

This public page shows a bounded preview of a large source file. The complete source remains in the raw and normalized source layers named in metadata, with the SHA-256 hash above for verification.

• Source characters: 260003
• Preview characters: 11932

Local absolute paths are redacted in this public view. The source hash and source-side raw layer are based on the unredacted source file.

uai: 1.0
type: progress
project: Protocol5
updated: 2026-05-08

protocol5_iota_strategy_public_api_tooling_2026_05_16:
  status: verified
  intake:
    - Refreshed active intake with scripts/Invoke-UaiFileIntake.ps1 and reviewed six Improvement documents for the Protocol5 IOTA-1 implementation pass.
    - Applied Comprehensive Evaluation of Protocol5.md to facade/API/UI/docs/test coverage.
    - Applied Deployment of Highly Compact Symbolic Systems with SQL Server 2025 and LM Studio.md to read-only SQL/LM Studio readiness boundaries and local-only embedding guidance.
    - Applied From Theory to IOTA Implementation.md selectively to HTML Keyless Extractor, Concept Bridge, claim boundaries, public tool DTOs, and agent guidance; private-use preview language remains outside the public-symbol boundary.
    - Applied Decoupled Symbolic Systems Deployment Architecture.md selectively to keyless JSON, integration outcome labels, SQL vector architecture notes, and public projection rules; blockchain/DID/VC remains future provenance plumbing only.
    - Applied Mapping Semantic Decoupling Patterns.md and Semantic decoupling.md as architecture and contract guidance for expression/concept separation, evidence traces, and safe public projection.
  work_completed:
    - Added public IOTA tooling models and logic for registry records, public seed concepts, Unicode validation envelopes, concept bridge results, HTML keyless extraction, steganography diagnostics, claim boundaries, and lightweight integration ledgers.
    - Wired active Protocol5.com host overlay routes under /api/iota while preserving /api/justaniota compatibility, including status, convert, round-trip, parse-glyphs, evidence, seed-vs-SQL, similarity, search, validate-symbol, HTML keyless extract, concept bridge, steganography scan, public registry, examples, and openapi summary.
    - Added payload size checks and public dependency error text that avoids SQL details, local paths, secrets, and private corpus internals.
    - Improved the active language converter overlay with public /api/iota endpoints, DatabaseOnly/Hybrid/LLM mode explanation, required examples, status readiness output, and phrase segment display.
    - Improved public pages and docs with hard rules, local-only embedding boundaries, public-symbol safety, keyless JSON, semantic decoupling, seed-vs-SQL, public projection, and machine guidance.
    - Added JSON schemas and representative examples for conversion, registry records, evidence, Unicode safety, seed-vs-SQL, semantic similarity, steganography, keyless envelopes, and package manifests.
    - Added focused MSTest coverage for public tooling, PUA rejection, HTML stripping, concept bridge, hidden-carrier detection, claim boundaries, and schema/example validation.
  hot_memory_update:
    - .uai/progress.uai
    - .uai/intake-index.uai
    - Protocol5.JustAnIota/Domain/PublicToolingModels.cs
    - Protocol5.JustAnIota/Logic/PublicIotaTooling.cs
    - CodexOverlay/Protocol5.com.Host/JustAnIotaApi.cs
    - CodexOverlay/Protocol5.com/SiteContent/Protocols/Iota/language-converter/index.html
    - CodexOverlay/Protocol5.com/SiteContent/js/iota-semantic-converter.js
    - Protocol5.com/SiteContent/Protocols/Iota/evidence/index.html
    - Protocol5.com/SiteContent/Protocols/Iota/protocol-rules/index.html
    - Protocol5.com/SiteContent/Protocols/Iota/steganography/index.html
    - Protocol5.com/SiteContent/llms.txt
    - docs/iota-*.md
    - Protocol5.com/SiteContent/schema/iota/*.schema.json
    - examples/iota/*.json
    - Protocol5.UAI.CSharp.Tests/JustAnIotaPublicToolingTests.cs
  long_memory_or_archive:
    - Processed Improvement source documents were moved to agent-file-handoff/Archive/2026-05-16/Improvement/iota-public-api-tooling/.
    - Refreshed .uai/intake-index.uai after archiving; active intake count is 0.
  checks_run:
    - powershell -NoProfile -ExecutionPolicy Bypass -File scripts/Invoke-UaiFileIntake.ps1
    - dotnet build Protocol5.JustAnIota/Protocol5.JustAnIota.csproj -c Debug --no-restore
    - dotnet build Protocol5.com.Host/Protocol5.com.Host.csproj -c Debug --no-restore -o artifacts/tmp-host-build
    - dotnet test Protocol5.UAI.CSharp.Tests/Protocol5.UAI.CSharp.Tests.csproj --no-restore --filter FullyQualifiedName~JustAnIotaSemanticInterlinguaTests
    - dotnet test Protocol5.UAI.CSharp.Tests/Protocol5.UAI.CSharp.Tests.csproj --no-restore --filter FullyQualifiedName~JustAnIotaPublicToolingTests
    - Local smoke checks against http://127.0.0.1:5107/api/iota/status, registry/public, concept-bridge, validate-symbol, html-keyless-extract, convert, and steganography/scan.
  checks_passed:
    - JustAnIota Debug build passed with 0 warnings and 0 errors.
    - Host build passed with alternate output path because the default output was locked by an already-running Protocol5.com.Host process.
    - Semantic interlingua focused tests passed.
    - Public tooling focused tests passed with 6 passed, 0 failed, 0 skipped.
    - Host build pre-target TypeScript compile and translation integrity tests passed.
    - Local smoke checks confirmed public registry status, concept bridge resolution, PUA validation failure, HTML extraction, conversion response shape, and hidden-carrier/PUA steganography detections.
  skipped:
    - Default host output build copy could not complete because Protocol5.com.Host PID 74312 held DLL locks; the alternate output build verified compilation without stopping the running server.
    - Live SQL Server vector integration, live LM Studio calls, production deploy, and publish staging were not run in this pass.

protocol5_embedding_desktop_input_suffix_eos_workaround_2026_05_08:
  status: verified
  intake:
    - Refreshed Protocol5 intake with scripts/Invoke-UaiFileIntake.ps1; no active Content or Improvement files required review.
  work_completed:
    - Added an explicit Protocol5.EmbeddingDesktop Input suffix setting as a controlled app-side workaround for local embedding models whose loader does not expose a request-side add_eos_token option.
    - Kept the suffix blank by default; when set, it is appended to every trimmed descriptor before LM Studio receives the batch, stored in Category.IotaEmbeddingRecords.DescriptorText, included in the descriptor hash, and used by status/stale/pending SQL comparisons.
    - Added run-summary visibility and a PROTOCOL5_EMBEDDING_INPUT_SUFFIX environment override without trimming the suffix, so deliberately chosen special-token text is preserved exactly.
    - Updated desktop README, JustAnIota hot memory, and focused contract tests to document that this is an escape hatch, while a fixed or freshly reconverted GGUF with correct EOS/SEP metadata remains the cleaner model-side fix.
    - Published a fresh side-by-side desktop build to [local path redacted] because the existing [local path redacted] process may still be running.
  hot_memory_update:
    - .uai/progress.uai
    - .uai/justaniota.uai
    - Protocol5.EmbeddingDesktop/MainWindow.xaml
    - Protocol5.EmbeddingDesktop/MainWindow.xaml.cs
    - Protocol5.EmbeddingDesktop/Models/EmbeddingAppSettings.cs
    - Protocol5.EmbeddingDesktop/Services/AppSettingsStore.cs
    - Protocol5.EmbeddingDesktop/Services/EmbeddingPopulationService.cs
    - Protocol5.EmbeddingDesktop/appsettings.json
    - Protocol5.EmbeddingDesktop/README.md
    - Protocol5.UAI.CSharp.Tests/JustAnIotaContractTests.cs
  long_memory_or_archive:
    - External AIWikis/LLM Wiki consolidation is not configured for this local desktop troubleshooting change.
    - No active intake source files were present to archive.
  checks_run:
    - powershell -NoProfile -ExecutionPolicy Bypass -File scripts/Invoke-UaiFileIntake.ps1
    - dotnet build Protocol5.EmbeddingDesktop/Protocol5.EmbeddingDesktop.csproj -c Debug --no-restore
    - dotnet test Protocol5.UAI.CSharp.Tests/Protocol5.UAI.CSharp.Tests.csproj --no-restore --filter FullyQualifiedName~JustAnIotaContractTests
    - rg scan for banned var usage across Protocol5.JustAnIota, Protocol5.EmbeddingDesktop, and the JustAnIota host API surface
    - rg scan for Entity Framework references across Protocol5.JustAnIota, Protocol5.EmbeddingDesktop, and Protocol5.com.Host
    - dotnet publish Protocol5.EmbeddingDesktop/Protocol5.EmbeddingDesktop.csproj -c Release --no-restore -o [local path redacted]
  checks_passed:
    - EmbeddingDesktop Debug build passed with 0 warnings and 0 errors.
    - Focused JustAnIota contract tests passed with 56 passed, 0 failed, 0 skipped.
    - No banned var usage or Entity Framework references were found in the checked JustAnIota/desktop/API C# surface.
    - Release publish completed to [local path redacted]
  skipped:
    - Live embedding population, public route checks, publish staging, production deployment, and release memory sorting were not run because this was a local desktop model-compatibility UI/provenance change, not a public-site or release/package change.

protocol5_embedding_desktop_qwen3_sep_warning_note_2026_05_08:
  status: verified
  intake:
    - Refreshed Protocol5 intake with scripts/Invoke-UaiFileIntake.ps1; no active Content or Improvement files required review.
  work_completed:
    - Investigated repeated LM Studio developer-log warnings during Protocol5.EmbeddingDesktop embedding population and confirmed the active local settings target LM Studio at http://127.0.0.1:1234 with model text-embedding-qwen3-embedding-8b, dimensions 1998, batch size 25, and embedding version justaniota-category-qwen3-8b-1998-v1.
    - Confirmed LM Studio has Qwen3 0.6B, 4B, and 8B embedding models loaded, with Qwen3 8B actively computing queued embedding work while the older [local path redacted] desktop process is running.
    - Added a Qwen3-specific advisory to the desktop Test LM result explaining that repeated SEP-token warnings indicate GGUF tokenizer metadata, and that the operator should use a fixed or reconverted GGUF with EOS/SEP metadata and bump the embedding version before regenerating rows.
    - Updated the desktop README and JustAnIota hot memory with the same operational rule, including the warning that app-side suffixing changes embedding provenance and should stay controlled rather than implicit.
  hot_memory_update:
    - .uai/progress.uai
    - .uai/justaniota.uai
    - Protocol5.EmbeddingDesktop/Services/EmbeddingPopulationService.cs
    - Protocol5.EmbeddingDesktop/README.md
  long_memory_or_archive:
    - External AIWikis/LLM Wiki consolidation is not configured for this local desktop troubleshooting note.
    - No active intake source files were present to archive.
  checks_run:
    - powershell -NoProfile -ExecutionPolicy Bypass -File scripts/Invoke-UaiFileIntake.ps1
    - lms ps --json
    - lms ls --embedding --json
    - Invoke-RestMethod http://127.0.0.1:1234/v1/models
    - dotnet build Protocol5.EmbeddingDesktop/Protocol5.EmbeddingDesktop.csproj -c Debug --no-restore
    - dotnet publish Protocol5.EmbeddingDesktop/Protocol5.EmbeddingDesktop.csproj -c Release --no-restore -o [local path redacted]
    - rg scan for banned var usage across Protocol5.JustAnIota, Protocol5.EmbeddingDesktop, and the JustAnIota host API surface
    - rg scan for Entity Framework references across Protocol5.JustAnIota, Protocol5.EmbeddingDesktop, and Protocol5.com.Host
  checks_passed:
    - EmbeddingDesktop Debug build passed with 0 warnings and 0 errors.
    - Release publish completed to [local path redacted]
    - No banned var usage or Entity Framework references were found in the checked JustAnIota/desktop/API C# surface.
  skipped:
    - Live embedding population, public route checks, publish staging, production deployment, and release memory sorting were not run because this was a local desktop warning/advisory pass, not a public-site or release/package change.

protocol5_embedding_desktop_discovery_timeout_hardening_2026_05_08:
  status: verified
  intake:

Why This File Exists

This is a UAI AI Memory handoff file from protocol5.com. 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 .uai file is a compact project context packet. It keeps one kind of durable project truth separate from the rest of the archive so an agent can load the topic it needs without pulling the whole project history into prompt context.

Structure

The file has no Markdown headings, so its path, frontmatter, file type, and provenance metadata carry most of the retrieval meaning.

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-699 (primary)
• Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "Progress",
    "source_site":  "protocol5.com",
    "source_url":  "https://protocol5.com/",
    "canonical_url":  "https://aiwikis.org/protocol5/files/uai-progress-uai-9368034c/",
    "source_reference":  ".uai/progress.uai",
    "file_type":  "uai",
    "content_category":  "uai-system",
    "content_hash":  "sha256:9368034c751b8fb23f3fa72fdec67022137a95bb4d10ac77c4fb2a9a7840a3af",
    "last_fetched":  "2026-06-22T01:56:21.9510185Z",
    "last_changed":  "2026-05-16T01:58:54.1536696Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-699",
    "duplicate_role":  "primary",
    "related_files":  [

                      ],
    "generated_explanation":  true,
    "explanation_last_generated":  "2026-06-22T01:56:21.9510185Z"
}