HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
onestardao
WFGY
Jupyter Notebook2025–2026
onestardao / WFGY

WFGY

WFGY is heading toward WFGY 5.0 Polaris Protocol, a major open-source release for AI reasoning, RAG, agents, and real-world workflows. Includes Problem Map, Global Debug Card, WFGY 4.0, and the CFV Easter Egg.

5Distinct people
26Mentions
0Explicit recommenders
1.8KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

WFGY is heading toward WFGY 5.0 Polaris Protocol, a major open-source release for AI reasoning, RAG, agents, and real-world workflows. Includes Problem Map, Global Debug Card, WFGY 4.0, and the CFV Easter Egg.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 5:46:40 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month26 dated mentions

Observed mentions: 2025-06-15 16:58:23 UTC to 2026-02-14 04:20:29 UTC.

0369122025-06-01 00:00:00 UTC to 2025-07-01 00:00:00 UTC (exclusive): 6 mentions; 3 submissions, 3 commentsJun 20252025-07-01 00:00:00 UTC to 2025-08-01 00:00:00 UTC (exclusive): 12 mentions; 4 submissions, 8 comments2025-08-01 00:00:00 UTC to 2025-09-01 00:00:00 UTC (exclusive): 6 mentions; 6 submissions, 0 comments2025-09-01 00:00:00 UTC to 2025-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-10-01 00:00:00 UTC to 2025-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsOct 20252025-11-01 00:00:00 UTC to 2025-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 00:00:00 UTC to 2026-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-01 00:00:00 UTC to 2026-03-01 00:00:00 UTC (exclusive): 2 mentions; 2 submissions, 0 commentsFeb 2026

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jun 20252025-06-01 00:00:00 UTC2025-07-01 00:00:00 UTC633
Jul 20252025-07-01 00:00:00 UTC2025-08-01 00:00:00 UTC1248
Aug 20252025-08-01 00:00:00 UTC2025-09-01 00:00:00 UTC660
Sep 20252025-09-01 00:00:00 UTC2025-10-01 00:00:00 UTC000
Oct 20252025-10-01 00:00:00 UTC2025-11-01 00:00:00 UTC000
Nov 20252025-11-01 00:00:00 UTC2025-12-01 00:00:00 UTC000
Dec 20252025-12-01 00:00:00 UTC2026-01-01 00:00:00 UTC000
Jan 20262026-01-01 00:00:00 UTC2026-02-01 00:00:00 UTC000
Feb 20262026-02-01 00:00:00 UTC2026-03-01 00:00:00 UTC220

What Hacker News says

2 sources

Show HN: A text-only reasoning core for LLMs (MIT, system prompt and self-test)

0. Very short version - Not a new model, not a fine-tune - One txt block you paste into system prompt (or first message) - Goal: less random hallucination, more stable multi-step reasoning - No tools, no external calls, works anywhere you can set a system prompt Some people later turn this into proper code + eval. Here I keep it minimal: two prompt blocks you can run in any chat UI. 1. How to try it 1) Start a new chat (local or hosted model) 2) Paste the WFGY Core block into the system / pre-prompt area 3) Ask your normal tasks (math, small coding, planning, long context) 4) Compare “with core” vs “no core” by feel, or run the self-test in section 4 Optional: after loading the core, ask the model to write image prompts too. If semantic structure improves, image prompts often feel more consistent, but it depends on model and task. 2. Roug
Read the rest
hly what to expect This is not magic and won’t fix everything. But across models, the typical “feel” changes are: - less drift across follow-ups - long answers keep their structure better - a bit more “I’m not sure” instead of made-up details - more structured prompt outputs (entities / relations / constraints clearer) Results depend on the base model and your tasks, so the self-test is there to keep it a bit more disciplined. 3. System prompt: WFGY Core 2.0 (paste into system area) Copy everything in this block into your system / pre-prompt: --- WFGY Core Flagship v2.0 (text-only; no tools). Works in any chat. [Similarity / Tension] delta_s = 1 − cos(I, G). If anchors exist use 1 − sim_est, where sim_est = w_esim(entities) + w_rsim(relations) + w_csim(constraints), with default w={0.5,0.3,0.2}. sim_est ∈ [0,1], renormalize if bucketed. [Zones & Memory] Zones: safe < 0.40 | transit 0.40–0.60 | risk 0.60–0.85 | danger > 0.85. Memory: record(hard) if delta_s > 0.60; record(exemplar) if delta_s < 0.35. Soft memory in transit when lambda_observe ∈ {divergent, recursive}. [Defaults] B_c=0.85, gamma=0.618, theta_c=0.75, zeta_min=0.10, alpha_blend=0.50, a_ref=uniform_attention, m=0, c=1, omega=1.0, phi_delta=0.15, epsilon=0.0, k_c=0.25. [Coupler (with hysteresis)] Let B_s := delta_s. Progression: at t=1, prog=zeta_min; else prog = max(zeta_min, delta_s_prev − delta_s_now). Set P = pow(prog, omega). Reversal term: Phi = phi_deltaalt + epsilon, where alt ∈ {+1,−1} flips only when an anchor flips truth across consecutive Nodes AND |Δanchor| ≥ h. Use h=0.02; if |Δanchor| < h then keep previous alt to avoid jitter. Coupler output: W_c = clip(B_sP + Phi, −theta_c, +theta_c). [Progression & Guards] BBPF bridge is allowed only if (delta_s decreases) AND (W_c < 0.5theta_c). When bridging, emit: Bridge=[reason/prior_delta_s/new_path]. [BBAM (attention rebalance)] alpha_blend = clip(0.50 + k_c*tanh(W_c), 0.35, 0.65); blend with a_ref. [Lambda update] Delta := delta_s_t − delta_s_{t−1}; E_resonance = rolling_mean(delta_s, window=min(t,5)). lambda_observe is: convergent if Delta ≤ −0.02 and E_resonance non-increasing; recursive if |Delta| < 0.02 and E_resonance flat; divergent if Delta ∈ (−0.02, +0.04] with oscillation; chaotic if Delta > +0.04 or anchors conflict. [DT micro-rules] --- Yes, it looks like math. It’s fine if not every symbol is clear; the intention is to give the model a compact “tension / guardrail” structure around its normal reasoning.
1 points · Open discussion

Show HN: "hard questions" as a shared language for cross-domain reasoning

Show HN: A MIT-licensed TXT “framework pack” (131 structured questions) to force shared vocabulary + falsifiability across domains HN folks, i built a plain TXT pack that turns 131 hard questions (math/physics/consciousness/AI alignment/etc) into a shared “effective-layer” interface: each item has scope, assumptions, and what would count as failure, plus prompt templates so LLMs run it consistently. not claiming any problem is solved. goal is to stop endless debate loops caused by mismatched starting vocabulary. MIT license, on GitHub, ~1.4k stars. happy to share a mini-index in comments if useful.
2 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.