Skip to content
aiWikis.org

Progress

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

Metadata

FieldValue
Source siteprotocol5.com
Source URLhttps://protocol5.com/
Canonical AIWikis URLhttps://aiwikis.org/protocol5/uai-system/files/uai-progress-uai-1c19fc0e/
Source reference.uai/progress.uai
File typeuai
Content categoryuai-system
Last fetched2026-05-08T21:22:18.3035107Z
Last changed2026-05-08T14:13:29.6808144Z
Content hashsha256:1c19fc0e2287592a11d06c19cc64dc5563c5699718a2a0ac7a498611d1759336
Import statusunchanged
Raw source layerdata/sources/protocol5/uai-progress-uai-1c19fc0e2287.uai
Normalized source layerdata/normalized/protocol5/uai-progress-uai-1c19fc0e2287.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: 255333
  • Preview characters: 11967

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_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 E:/Temp/EmbeddingApp-InputSuffix
  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 E:/Temp/EmbeddingApp-InputSuffix.
  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 E:/Temp/EmbeddingApp-QwenWarning
    - 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 E:/Temp/EmbeddingApp-QwenWarning.
    - 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:
    - Refreshed Protocol5 intake with scripts/Invoke-UaiFileIntake.ps1; no active Content or Improvement files required review.
  work_completed:
    - Hardened Protocol5.EmbeddingDesktop table discovery for the local Category corpus by extending lightweight schema, catalog, and status SQL command timeouts beyond the default 30-second cold-cache failure window.
    - Wrapped SQL command timeout failures during discovery with step-specific messages so the activity log reports whether the timeout happened while preparing lightweight schema, reading table/vector metadata, or reading a specific table status.
    - Confirmed source-side DiscoverTablesAsync works against PLUTO/MSSQLSERVER2025 / Protocol5 and published a fresh side-by-side local desktop build to [local path redacted] because the older [local path redacted] process was still running and locked.
  hot_memory_update:
    - .uai/progress.uai
    - .uai/justaniota.uai
    - Protocol5.EmbeddingDesktop/Services/EmbeddingPopulationService.cs
    - Protocol5.EmbeddingDesktop/MainWindow.xaml.cs
    - 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 bugfix.
    - 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
    - Live DiscoverTablesAsync smoke against PLUTO/MSSQLSERVER2025 / Protocol5 through .tmp/embedding-discover-smoke
    - dotnet publish Protocol5.EmbeddingDesktop/Protocol5.EmbeddingDesktop.csproj -c Release --no-restore -o E:/Temp/EmbeddingApp-DiscoveryFix
  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.
    - Live discovery completed in 30.19 seconds and returned Category.Categories/CategoryName with 727611 pending rows, Category.Words/Word with 172827 pending rows, and Category.ISO10646/Glyph with 0 pending rows.
    - Release publish completed to E:/Temp/EmbeddingApp-DiscoveryFix.
  skipped:
    - Live LM Studio embedding population, public route checks, publish staging for Protocol5.com, production deployment, and release memory sorting were not run because this is a local WPF desktop discovery bugfix.

protocol5_embedding_desktop_start_preflight_skip_2026_05_08:
  status: verified
  intake:
    - Active Protocol5 intake had already been refreshed for the desktop follow-up; no active Content or Improvement files required review.
  work_completed:
    - Investigated the reported running desktop state from the screenshot: the open process was still [local path redacted] not the newer side-by-side discovery-fix build, and it showed no active Protocol5 SQL request or LM Studio TCP connection at the time of inspection.
    - Changed Protocol5.EmbeddingDesktop Start preflight so selected tables that already report 0 metadata gaps skip the heavyweight deterministic semantic metadata refresh before LM Studio work.
    - Kept the semantic assertion quality gate for Category.Categories embedding work and for runs that actually perform metadata refresh, while allowing Words/ISO-only runs with current metadata to proceed directly toward embedding batches.
    - Published a fresh side-by-side local desktop build to [local path redacted] because the older [local path redacted] process was still running and locked.
  hot_memory_update:
    - .uai/progress.uai
    - .uai/justaniota.uai
    - Protocol5.EmbeddingDesktop/Services/EmbeddingPopulationService.cs
    - 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 bugfix.
    - No active intake source files were present to archive.
  checks_run:
    - Process inspection for running Protocol5.EmbeddingDesktop instances.
    - SQL Server active request and lock inspection for the Protocol5 database.
    - 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 E:/Temp/EmbeddingApp-StartFix
  checks_passed:
    - EmbeddingDesktop Debug build passed with 0 warnings and 0 errors.
    - Focused JustAnIota contract tests passed with 56 passed, 0 failed, 0 skipped.

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

Provenance And History

  • Current observation: 2026-05-08T21:22:18.3035107Z
  • Source origin: current-source-workspace
  • Retrieval method: local-source-workspace
  • Duplicate group: sfg-080 (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/uai-system/files/uai-progress-uai-1c19fc0e/",
    "source_reference":  ".uai/progress.uai",
    "file_type":  "uai",
    "content_category":  "uai-system",
    "content_hash":  "sha256:1c19fc0e2287592a11d06c19cc64dc5563c5699718a2a0ac7a498611d1759336",
    "last_fetched":  "2026-05-08T21:22:18.3035107Z",
    "last_changed":  "2026-05-08T14:13:29.6808144Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-080",
    "duplicate_role":  "primary",
    "related_files":  [

                      ],
    "generated_explanation":  true,
    "explanation_last_generated":  "2026-05-08T21:22:18.3035107Z"
}