WFGY 5.0 Polaris Protocol
A governed protocol layer for AI reasoning, RAG, and agents, with staged rollouts and public evidence.
- Source repo
- onestardao/WFGY
- Stars
- ★ 1.8k
- Last updated
- 1d ago
- License
- NOASSERTION
- Primary language
- Jupyter Notebook
- FA score
- 22/100 · Major gaps
At a glance
- How it runs
- Works with
- Universal · cross-platform
- Cost
- Free software; you pay for model usage
- Setup effort
- Low · running in minutes
- Typical use
- Developers facing hallucinations or broken workflows in RAG or agent pipelines can use Problem Map 3.0 and Global Debug Card for structured diagnostics.
- Not a fit if
- Teams needing executable code or automated installation
- Teams requiring a clear license for commercial use
- Teams needing the complete engine, not a staged rollout
- Source review
- 22/100 · Major gaps 8 safety controls not found
What does this agent do, and when should you use it?
WFGY is an open-source ecosystem currently led by WFGY 5.0 Polaris Protocol, providing a governed protocol layer for building, tuning, verifying, and carrying structured language systems across sessions, tasks, and worlds. The repository includes layered versions: 3.0 as frontier reasoning and verification (Event Horizon), 4.0 as governance engine (Twin Atlas, Inverse Atlas, AI Eval), and 5.0 conducting a staged functional rollout of evidence packages, portable protocol components, and reproduction materials. Public components include Polaris Experiments, the Cite First Verification easter egg, and the Polaris Goal Compiler, the first portable protocol component. Additionally, Problem Map 3.0 provides a rapid troubleshooting gate for broken AI workflows with Atlas Router, Global Debug Card, and Global Fix Map.
WFGY 5.0 Polaris Protocol releases components batch-by-batch. Polaris Experiments provide public evidence packages with raw outputs, parsed outputs, verdicts, audits, token records, and hashes. Polaris Goal Compiler is a portable human-AI execution protocol that compiles user goals before construction, separates truth work from expression work, exposes active and blocked downstream work, prevents premature completion claims, and verifies before unlocking. Cite First Verification easter egg verifies the official TXT pack via SHA256 and outputs a specific boot block upon match. Problem Map 3.0 offers Atlas Router TXT, Global Debug Card, and Global Fix Map for diagnosing and fixing RAG or agent pipelines.
- Developers facing hallucinations or broken workflows in RAG or agent pipelines can use Problem Map 3.0 and Global Debug Card for structured diagnostics.
- AI engineers needing to prevent premature completion claims in multi-step tasks can adopt Polaris Goal Compiler as an execution policy.
- Researchers requiring reproducible evidence can download Polaris experiment packages and verify SHA256 hashes.
- Teams wanting to verify integrity of WFGY 3.0 TXT pack can use the Cite First Verification process with an LLM.
- Governance or compliance teams can reference WFGY 4.0's Twin Atlas and AI Eval for evaluation discipline.
- Developers building cross-session consistent agent behavior can adopt WFGY 5.0 protocol layers.
How do you install or deploy this agent?
This repository is primarily documentation and protocol references; there is no traditional installation package. To use Polaris Goal Compiler, clone the repo or directly download the Polaris/protocols/goal-compiler/README.md content, then paste it into your AI assistant, agent rule file, or workflow policy. Alternatively, start with Problem Map 3.0 by reading the troubleshooting atlas.
How do you use this agent?
- Clone the repository:
git clone https://github.com/onestardao/WFGY.git. 2. For Polaris Goal Compiler, copy the protocol content into your AI system's configuration, following its steps for compiling goals, separating work, and verifying. 3. For Cite First Verification, download the official TXT packWFGY-3.0_Singularity-Demo_AutoBoot_SHA256-Verifiable.txt, upload it to an LLM that can read files, and request verification of the SHA256 against the canonical value58dbd432db3e6494364557257f7ce068eb59bdd039995dff4c281d655f7d464f. The AI should output the designated boot block if matched. 4. For Problem Map 3.0, follow the Atlas Router and Global Debug Card guidance to diagnose issues.
What are this agent's strengths and limitations?
- Staged rollout model makes useful components available early, allowing users to test practical pieces before a full release.
- Public evidence-first approach with downloadable experiment packages, hashes, and audit records enhances verifiability.
- Polaris Goal Compiler is a portable protocol that can be integrated into any AI system without vendor lock-in.
- Problem Map 3.0 offers a structured troubleshooting path for common AI failures, reducing debugging effort.
- Currently provides mainly protocols and documentation, lacking executable code or automated installation, requiring manual integration.
- Polaris experiments have not been independently verified, which may fall short of strict reproducibility standards.
- The staged release leaves deeper engine layers and runtime structures pending, so the full system is incomplete.
- The license is marked NOASSERTION, requiring legal review before use; this may deter commercial adoption.
How does this agent compare with similar options?
Compared to LangChain and AutoGPT, WFGY emphasizes protocol and structured language rather than chain orchestration or autonomous agents; it includes built-in debugging and verification frameworks, whereas LangChain and AutoGPT lack built-in verification layers.
Key facts side by side with the most closely related agents.
| Agent | Source review | Form / cost | Stars | Updated | Language | Full support on |
|---|---|---|---|---|---|---|
| WFGY 5.0 Polaris Protocol This agent | 22 · Major gaps | Agent plugin / skillFree + model costs | ★ 1.8k | 1d ago | Jupyter Notebook | — |
| MCP Memory Service | 68 · Some gaps | MCP serverFree | ★ 2k | today | Python | ChatGPT · Codex · Claude Code · Claude.ai |
| Agent Memory Techniques | 57 · Major gaps | Library / SDKFree + model costs | ★ 1.1k | 1d ago | Jupyter Notebook | — |
| RepoBrain – Repo Intelligence Engine | 49 · Major gaps | Agent plugin / skillFree + model costs | ★ 1.4k | 3d ago | Python | Codex · Claude Code |
How does FollowAgents rate this agent?
Why each dimension lost points
Evidence shows a security policy and an auto-reply workflow, but no code or execution details are provided. There is no least privilege, no user confirmation, no data flow transparency, no sensitive data handling, no dependency security, no external effects control, no rollback, and no source attribution. Therefore all trust criteria score 0.
Self-consistency: README mentions 'Polaris Goal Compiler' and 'Problem Map 3.0' multiple times, but link paths are inconsistent (e.g., './Polaris/protocols/goal-compiler/README.md' vs './Polaris/README.md'), and FAQ has inconsistent capitalization (e.g., './Recognition/' vs './recognition/'), so score 1. Dependency availability: no dependencies mentioned, score 0. Failure messages: no error handling or failure message examples, score 0.
Audience and scenarios: README clearly lists various user scenarios and routing, score 2. Capability boundaries: describes protocol layer and components but not explicit boundaries, score 1. Trigger precision: provides AI routing instructions and verification steps but not explicit triggers, score 1. Environment fit: no supported environments or platforms mentioned, score 1.
Information architecture: README is well-structured with navigation and FAQ, score 2. Install notes: no installation or usage instructions, score 0. Naming stability: version naming is clear but some links have inconsistent capitalization, score 1. Examples and FAQ: provides FAQ and examples, score 2. Known limitations: none mentioned, score 0. License: LICENSE file exists but metadata is NOASSERTION, and license text is MIT, score 1. Versioning and changelog: no changelog provided, score 1. Maintenance responsibility: README mentions maintainers but not explicit responsibility, score 1.
Output usability: provides protocol components and evidence packages but no output format, score 1. Marginal value: provides unique protocol layer and evidence-first approach but no comparison with other tools, score 1. Cost-benefit: no performance or cost data, score 1.
Claim traceability: provides SHA256 checksum and evidence packages but no raw data, score 1. Cross-source corroboration: no external verification, score 0. Fact-inference separation: README distinguishes facts and inferences but not explicitly labeled, score 1.
- Not found in source: least-privilege scopingGrant only what the task needs: a dedicated account or read-only token, scoped to specific directories and repos.
- Not found in source: confirmation before actingTurn on (or add) a confirmation step before it acts, and try it in a sandbox or test environment before real data.
- Not found in source: data-flow disclosureWatch which external services it contacts (proxy or firewall logs) and keep sensitive data out until you know where it goes.
- Not found in source: sensitive-data handlingUse dedicated, low-privilege, revocable API keys — never production credentials — and keep secrets out of logs.
- Not found in source: dependency securityPin versions and run a dependency audit (npm audit, pip-audit) before installing; prefer running it in a container.
- Not found in source: disclosed external effectsEstablish which external systems it writes to, sends to or changes, and verify with test accounts or repos before production.
- Not found in source: rollback or recovery pathBack up first, or work on a git branch or snapshot, so its changes can be undone.
- Not found in source: verifiable attributionInstall from the official repo or registry and check the publisher and URL to avoid look-alike packages.
- The repository provides no executable code or tests, so functionality cannot be verified.
- License metadata is NOASSERTION, despite an MIT license file, which needs confirmation.
- Inconsistent link paths may cause navigation issues.
- No installation or usage instructions are provided, making it hard for users to get started.
Recent releases
Latest entries from the project's GitHub Releases. Notes are quoted from upstream as written, not rewritten or tested by FollowAgents.
-
v5.0.0-teaser-01 WFGY 5.0 Teaser 01: Polaris Goal Compiler
Release notes excerpt
WFGY 5.0 Teaser 01: Polaris Goal Compiler <img width="1672" height="941" alt="polaris_goal_compiler" src="https://github.com/user-attachments/assets/083f5735-8313-42c1-8a7f-ac406ddfe33a" /> This is the first small public teaser release in the staged WFGY 5.0 Polaris Protocol rollout. WFGY 5.0 has grown beyond a single release package. Instead of waiting for one giant drop, we are now releasing useful components step by step so users can inspect, test, and understand each part properly. …View on GitHub ↗ -
WFGY-Easter-Egg-CFV WFGY Easter Egg: Cite First Verification
Release notes excerpt
WFGY Easter Egg: Cite First Verification v0.1.0 Before WFGY 5.0 Polaris Protocol officially arrives, I want to share a small gift with everyone who has supported WFGY along the way. WFGY 5.0 is a major release built from the full path of WFGY 1.0, 2.0, 3.0, and 4.0, plus everything I, PSBigBig, have learned through this long journey. This road has not been easy. To make WFGY 5.0 stronger, cleaner, and more polished, the official launch will take a little more time. So before the main release goes online, here is a small Easter Egg: Cite First Verification …View on GitHub ↗ -
WFGY-4.0 WFGY 4.0 · Twin Atlas + Inverse Atlas Public Release
Release notes excerpt
WFGY 4.0 is the first public release surface in this repository where the engine-level view becomes legible as one direction rather than a scattered set of ideas. This release brings two major public surfaces into focus together: - Twin Atlas - Inverse Atlas They are related, but they are not duplicates. Twin Atlas is the flagship engine view. Inverse Atlas is the legitimacy-first governance methodology that pushes the control point forward, before stronger public emission is allowed. What this release is really about …View on GitHub ↗