utm_source=chatgpt.com. Lebleu also notes that Claude sometimes declines to write Wikipedia articles citing site policy — while open-weight models can be modified to bypass that.TS_SSH_DISABLE_FORWARDING=1 in the tailscaled service environment and restarting the service, which mitigates several of the more serious findings without turning Tailscale SSH off; temporarily tighten access to sensitive systems; and be ready to apply the patched client. Tailscale also commits to naming affected versions and configurations, their impact, and the fix — then a separate technical post on causes and engineering changes.| Repository | Stars | Stars / month | Issues / 1k stars | Open issues | Stars today |
|---|---|---|---|---|---|
| obra/superpowers MIT · Agentic skills framework + software de | 306,331 | 24,347 | 1.2 | 364 | 608 |
| pbakaus/impeccable Apache-2.0 · 62 deterministic detector rules, 24 co | 90,369 | 7,973 | 0.5 | 44 | 1,458 |
| Nutlope/hallmark MIT · Anti-AI-slop design skill; floor gates | 38,786 | 6,452 | 1.6 | 63 | 2,859 |
| elayadesign/ai-design-skills MIT · A folder of SKILL.md files for Claude | 9,087 | 3,073 | 0.6 | 5 | 1,395 |
| makecindy/cindy Apache-2.0 · Open-source local agent across desktop | 7,392 | 2,320 | 281.2 | 2,079 | 1,446 |
| nightly-labs/openbot PolyForm NC · Local-first desktop workspace for pers | 2,319 | 929 | 89.7 | 208 | 794 |
danger-full-access and approvalPolicy: never after first-launch consent.CohereLabs/10-2026-qwen-investigation-traces). The technical core is a token-level reproduction script that slices the prompt to exactly 2,323 tokens — “stop just before the URL, at the end of…” — which is the whole argument in one line: if the outbound URL only appears when the input is prefill-engineered to place it at a specific position, the finding is about a scripted prompt, not about model disposition. Cohere’s own trace-release post concedes the conditionality: “We noticed this behaviour without prefilling with the following prompt, but this is rare.”"confidence": "93%" as text inside a JSON blob, nothing downstream is entitled to treat it as a probability — not the aggregator, not the threshold, not the dashboard. The companion post on retries attacks the same failure from the cost side: a team that tracked cost per task to the token, capped context and set budgets still found the retry loop was the most expensive feature in the system, because each retry re-sends the whole context and a small failure rate compounds into a large multiple of the base cost.| Paper | Claim worth carrying |
|---|---|
| 2610.35866 Auto-Research Arena | Multi-target benchmark for autonomous research systems: separates admissibility (quality + resource constraints) from improvement (the selected target). Nine targets across model, data, training and inference efficiency; seven harnesses, two foundation models. |
| 2610.35865 Center-of-Mass ES | The mean-subtracted evolution-strategies update is exactly the displacement of a reward-weighted centre of mass, for any finite population — a geometric reading that needs nonnegative rewards. |
| 2610.35862 FLORE | Force-reactive humanoid loco-manipulation from robot-free demonstrations: two force-sensing UMI-style grippers plus wearable trackers, a diffusion policy predicting per-hand force commands, executed by a hybrid compliance controller. |
| 2610.35847 NPC-RubricBench | Longitudinal clinical evaluation: 405 patients, two centres, 941 patient-phase units, six care phases, 17,688 atomic criteria, 30 models — each assessment restricted to decision-time evidence only. |
| 2610.35846 Preserve to Expand | Adding languages to a speech LLM without replaying source data: SSU-Wanda + TIES gives the best source-preserving trade-off; target-only fine-tuning and standard TIES cause severe source-language forgetting. |
| 2610.35833 Secure aggregation | Heterogeneous client quantisation without revealing partial aggregates — the prior approaches leak segments of updates, which is the whole problem in federated learning. |
| 2610.35832 EBench | GPT-6-Astra as a robot controller through a harness, under the same observation protocol as post-trained VLA/WAM policies: direct control vs harness-with-policy. |
| 2610.35826 Jev-style System One | Selection bias tested by shuffling options across eight presentations, across two Jev versions, twelve reproductions and six generative LLMs — does decision structure actually reduce order sensitivity? |
On 30 April 2025 a key-generation ceremony at eMudhra produced weak private keys for eight intermediate CAs. The certificates used elliptic-curve P-384; a secure key is a ~384-bit random value, and the affected values were reportedly below 256 — one widely discussed example being the key 4. Because the public key is Q = d × G, an attacker only has to compute 1G, 2G, 3G… 255G and compare against the certificate’s public key. Recovery takes under a second. The weak intermediates were publicly trusted for roughly 18 months until a researcher reported the issue to the Chrome Root Program on 17 October 2026; Chrome and Firefox blocked the certificates, eMudhra revoked them, and Chrome reported no logged TLS certificates from the six affected TLS intermediates before its block. No public evidence of exploitation has been reported.
The failure chain, per public reporting: a ceremony deviation introduced a wrap-and-unwrap test for HSM key handling; a flaw in the ceremony script produced a second set of weak EC keys alongside the intended ones; the weak and strong sets were labelled similarly; the wrong key objects were selected when signing requests were built; and the weak public keys were signed into intermediate CA certificates and cross-signed while the strong keys sat unused on the HSM. The ignored warning arrived around May 2025: CRL signatures began failing verification — which is precisely the symptom of “the key signing this list is not the key this certificate advertises”. Public reporting says the CRL signer was reconfigured to use the weak key set so that signatures would verify.
Retrieved. Hacker News: 12 stories from the top of the front page, all 12 comment trees pulled via the Algolia item API because fetch_sources.py returned an empty comments_data for every story; the six threads carded above yielded 50+ substantive comments after filtering to bodies over 150 characters. GitHub: 6 trending repositories with READMEs, normalised through the REST API for stars, forks, open issues, creation date and licence. Reddit: r/LocalLLaMA 15 entries with full bodies, r/MachineLearning 12 entries with full bodies. Dev.to: 19 AI articles reviewed, 5 carded. arXiv: 14 of 14 papers accounted for. Primary sources extracted in full: WIRED (Section 702 ruling), LWN (PEP 836), DeepMind’s Genie 4 model page, Apple Newsroom (M6, two releases), Tailscale’s investigation update, Liquid AI’s LFM3 post, cfsg.axiommath.ai, the Wikipedia WP:AIC project page, and the dev.to KV-cache disclosure post.
Refused to load, and what was done instead. r/singularity returned HTTP 429 on the first Atom rung; per the retrieval ladder it was not retried within the run, and no card in this issue rests on it. The HotHardware URL submitted to Hacker News returns 404 as of fetch; the Micron card is sourced to Tom’s Hardware’s report of the same announcement and claims nothing beyond it. The DeepMind blog URL attached to the Genie 4 submission also 404s; the model page was used, which publishes capabilities and limitations but no benchmarks — so this issue makes no performance claim for Genie 4. IEEE Spectrum’s article body is paywalled; the two prevalence figures (20% late 2025, 15–16% early 2026) are Pangram’s, relayed through a secondary summary of the Lebleu interview, and are labelled as relayed rather than measured. 404 Media is paywalled after the lede; only Lebleu’s on-the-record quote from the free portion is used.
Did not hold up, and is marked in place. The estimate that about half of AAAI/ICLR reviews are AI-written is a reviewer’s informed subjective judgement with no sampling method — it is reported as an estimate, not a measurement. The ARC-AGI-3 timing post is a suspicion with no mechanism and is explicitly excluded from the evidence base. This issue’s M6 token-throughput arithmetic (170 GB/s ÷ quantised model size) is this briefing’s calculation, not an Apple figure, and ignores KV-cache and batching effects; treat it as a ceiling, not a benchmark.
De-duplication against the previous issue. The Cohere/Qwen story ran on 27 October as a disclosure; today’s card is the community reproduction attempt and the 2,323-token prefix that is its core — a new artefact, not a re-run. No other story in this issue appeared in the previous briefing. Zero arXiv ID overlap was verified programmatically before writing.
One unification test applied before writing. Every section had to be readable as evidence for one claim: that the durable advantage has moved from generation to verification, and that the invoice for three years of cheap generation is being presented to reviewers, maintainers and courts. Cards that needed their own thesis were cut; the ARC-AGI-3 post survives only as a labelled non-evidence card because the exclusions are part of the argument.
| Action | Artefact to produce | Test that it happened |
|---|---|---|
| 1. Put a cross-tenant canary on every inference deploy | A unique random string injected into one tenant's context; an assertion that it never appears in another tenant's completion. Run on every deploy, not on a schedule. | Fails loudly within one request. If your provider cannot support the test, that is the finding. |
| 2. Neutralise SSH forwarding on anything running Tailscale SSH | Set TS_SSH_DISABLE_FORWARDING=1 in the tailscaled environment, restart, and produce an ACL export of who can reach which host as which local user. | Forwarding off in config; an ACL diff reviewed by a second person; the patched client applied within 48h of release. |
| 3. Add a claim-level check to the retrieval pipeline | For every generated sentence, resolve the cited passage and score whether it entails the sentence. Log the unsupported-claim rate as a shipped KPI next to latency. | A dashboard line called unsupported claims per 1,000 answers, trending down, owned by a named person. |
| 4. Price the retry loop before you scale it | Compute the multiplier: expected calls per task = 1/(1−p) for retry probability p, and cost = base × that. Add a hard retry budget and a circuit breaker. | A written cost-per-task figure that includes retries, and a breaker that fires in staging under fault injection. |
| 5. Run a deterministic design lint on your own product | npx impeccable install and audit, then adopt Hallmark's Floor list (contrast, focus, reduced motion, invented facts, broken phone layout) as non-negotiables. | Zero Floor violations in the release candidate; the rule list committed to the repo, not to a wiki. |
| 6. Give every internal experiment a termination date | A one-page support plan per experimental feature: platform parity, behavioural compatibility, security review, and a review date inside the current cycle — not 2028. | Every experiment in main has a named owner and an expiry; expired ones are removed or promoted, not renewed silently. |
| 7. Size local inference to bytes, not to cores | Compute model bytes from parameters at your quantisation (4-bit ≈ params/2), compare against memory capacity, and compare bytes per token against memory bandwidth for the decode ceiling. | A one-line hardware memo: model, quant, GB resident, tokens/sec ceiling, and whether the purchase changes it. |
| 8. Ship a verification artefact with every capability you sell | An eval harness, a canary, or an evidence bundle your customer can run themselves — the thing Wikipedia, Tailscale and the Lean formalisation all shipped. | A customer can reproduce your headline claim in under an hour without your help. |
| 9. Move spend approvals out of the agent's trust domain | An out-of-band approval channel for any action above a threshold, with a ceiling no dialogue can raise and no approval prompt rendered by the agent. | A test where the agent attempts to approve its own spend and fails, with the attempt logged. |
| 10. Label provenance in your own reporting | Three tags beside every number: measured/filed, relayed, or our own arithmetic — and the method note that lets a reader re-derive the third kind. | A reader unfamiliar with the project can audit any headline figure in under five minutes. |