Skip to main content

Current Task Sync

This page prevents duplicate work across parallel StegVerse build sessions working on StegVerse-Labs/admissibility-wiki.

Source Of Truth Order​

1. docs/ADMISSIBILITY_WIKI_MIRROR_HANDOFF.md
2. docs/governance/current-task-sync.md
3. docs/governance/wiki-section-completeness-audit.md
4. exact repository files and generated evidence

The mirror handoff remains authoritative when this page or an older task statement conflicts with it.

Current GitHub Pages Target​

https://stegverse-labs.github.io/admissibility-wiki/
url: https://stegverse-labs.github.io
baseUrl: /admissibility-wiki/
custom_domain: not_configured
static/CNAME: removed

Current Assessment Goal​

Complete the wiki section-by-section completeness audit and remediate exact gaps in scope, coordinates, evidence posture, reproducibility, status language, authority boundaries, navigation, and maintenance ownership.

The audit order is maintained in:

docs/governance/wiki-section-completeness-audit.md

The current active block is:

Governance overview, current status, validation, and handoff surfaces

The next block is:

Governed LLM and governed ecosystem transition pages

Current Activation Goal​

Publish and validate the Admissibility Wiki as the public vocabulary, terminology convergence, proposal-review, proposal-intake, proof-path, external-framework input-class, governed ecosystem transition, and governed LLM topology site.

Activation remains evidence-bound. Repository source, generated pages, workflow artifacts, deployment, public URL verification, proof receipts, and custody evidence must remain distinguishable.

Installed Activation Structure​

Displayed without leading-dot paths for iOS readability. Actual repository paths beginning with github/ use a leading .github/ directory.

docs/activation/github-pages-cloudflare.md
static/status/admissibility-wiki-activation.json
static/status/admissibility-wiki-status.json
static/status/public-activation-receipt.example.json
static/status/workflow-receipt-automation-status.json
static/status/workflow-evidence-status.json
static/status/proposal-core-lite-target-watch-status.json
static/status/no-manual-task-guard-status.json
static/status/mirror-handoff-guard-status.json
static/status/governed-ecosystem-transitions-status.json
static/status/external-framework-input-class-status.json
static/status/canonical-workflow-observation-automation.json
static/status/canonical-workflow-observation-rollup.json
reports/pages-build-receipt.json
github/workflows/validate-chain-continuation.yml
iosnoperiod/github/workflows/validate-chain-continuation.yml
workflow_manifest.json
docs/CHAIN_AUTO.json
docs/CI_EVIDENCE.json
docs/GOAL_STATE.json

Single Workflow Policy​

Only one active GitHub Actions workflow is intended to exist:

.github/workflows/validate-chain-continuation.yml

The iOS-safe mirror is inert and exists only for copied path readability:

iosnoperiod/github/workflows/validate-chain-continuation.yml

Workflow sprawl is guarded by:

scripts/check_workflow_sprawl.py

Governed Ecosystem Transition Framing​

input or request
  -> governed ingestion
  -> CGE fingerprinting
  -> GCAT / BCAT evaluation
  -> Transition Table standing
  -> ALLOW / DENY / FAIL-CLOSED
  -> receipt_chain / STRP record
  -> governed output

Installed pages and status:

docs/governance/governed-ecosystem-transitions.md
docs/governance/external-frameworks-as-input-class.md
static/status/governed-ecosystem-transitions-status.json
static/status/external-framework-input-class-status.json
scripts/check_governed_ecosystem_transitions_status.py
scripts/check_external_framework_input_class_status.py

Governed LLM Topology​

The public activation map must include all participating coordinate classes rather than only the wiki, adapter, and SDK:

entry surfaces
-> governed request production
-> LLM-adapter runtime boundary
-> SDK contract and intake
-> formalism and admissibility authority
-> custody and reconstruction
-> public doctrine and verification
-> deployment and explicitly authorized execution

Current primary page:

docs/governance/governed-llm-activation-map.md

External Framework Evidence Posture​

External frameworks remain one governed input class. The public results surface must classify evidence strength and must not imply an independently reproducible comparison unless the full reproducibility gate is satisfied.

MENTION_ONLY
AUTHOR_COMMENTARY
SOURCE_REVIEWED
ARTIFACT_REVIEWED
PARAMETERIZED_OBSERVATION
REPRODUCIBLE_COMPARATIVE_TEST

Current public results surface:

docs/external-frameworks/evaluation-results.md

Current repository claim:

No independently reproducible external-framework comparative evaluation is presently claimed on that page.

Declarative External Framework Pipeline​

framework manifest
  -> generated compatibility report
  -> generated evaluation results page
  -> generated framework page-status block
  -> Docusaurus build
  -> GitHub Pages deploy
  -> public URL verification

Installed generators and validators include:

scripts/generate_external_framework_reports.py
scripts/generate_external_framework_results.py
scripts/generate_external_framework_page_status.py
scripts/check_external_framework_reports.py
scripts/check_external_framework_report_coverage.py
scripts/check_external_framework_report_generation.py
scripts/check_external_framework_results_page.py
scripts/check_external_framework_page_status.py
scripts/check_external_framework_terminology.py
scripts/check_external_framework_expansion_policy.py

Generated status or result language remains evidence only. It does not grant certification, endorsement, formalism adoption, admissibility proof, execution authority, or canonical STRP admission.

Aggregate Validation​

npm run validate

The canonical workflow owns full validation, generated artifacts, build, deployment, and public re-observation. A passing local validator is not a passing canonical chain.

Known Public Coordination Pages​

Do not recreate these pages under alternate names:

docs/index.md
docs/ADMISSIBILITY_WIKI_MIRROR_HANDOFF.md
docs/governance/current-visible-updates.md
docs/governance/current-task-sync.md
docs/governance/wiki-section-completeness-audit.md
docs/governance/validation.md
docs/governance/governed-ecosystem-transitions.md
docs/governance/governed-llm-activation-map.md
docs/governance/external-frameworks-as-input-class.md
docs/external-frameworks/index.md
docs/external-frameworks/evaluation-results.md

Known Remaining Installation And Review Targets​

StegVerse-Labs/admissibility-wiki:
  - complete Governance section audit
  - audit governed LLM and ecosystem transition pages
  - audit every external-framework page and machine-readable report
  - audit Formalisms, Glossary, Activation, Research, Social, and StegVerse sections
  - detect orphan pages and registry omissions
  - reconcile cross-repository status claims
  - observe canonical workflow and public evidence when exposed

Data-Continuation/formalism-tests:
  - add optimization-target fixtures and FAIL_CLOSED proof receipts only when its handoff authorizes work

StegVerse-Labs/Site:
  - mirror only after wiki evidence and the current Site handoff authorize propagation

GCAT-BCAT-Engine/Publisher:
  - queue publication awareness only after wiki evidence and current Publisher handoff authority

StegVerse-002/stegguardian-wiki:
  - defer interpretation until executable proof fixtures and destination handoff authority exist

Current Continuation Rule​

  1. Read the mirror handoff first.
  2. Continue the active completeness-audit block.
  3. Verify exact file presence and current content before creating or replacing files.
  4. Repair exact stale, incomplete, unsupported, or conflicting documentation without weakening validation.
  5. Preserve one active workflow and fail-closed evidence posture.
  6. Do not create manual route checks, workflow triggering, receipt construction, archival, file movement, or downstream propagation tasks for the user.
  7. Do not claim workflow pass, deployment pass, public reachability, custody, release, or execution authority without repository-owned evidence.

Current Redundancy Posture​

This repository may be touched by more than one session. Do not assume a previously proposed next step is still missing. Verify current repository state, then continue from the first unresolved audit item or exact deterministic failure.