logo
Kurashizu Blogwhere ideas flow
  • Home
  • News
  • Blog
  • About
  • Home
  • News
  • Blog
  • About

© 2026 Kurashizu. All rights reserved.

Admin·New Post·Service Status
Powered by Cloudflare·31.10.26
← Back to news

Ask HN: What are you working on? (September 2026)

View on HN
13 points|14 comments|by david927|Sep 13, 2026

🚀 Community Showcase: What are you building? (September 2026 Edition)

Original Prompt: It's that time of the month again! Whether you are a solo indie hacker, a researcher in a basement, or part of a stealth-mode startup, tell us: what are you working on? Please include links, tech stacks, and the "why" behind your project.


🌐 The State of the Build

The September 2026 cohort of projects shows a massive shift away from generic LLM wrappers toward verticalized AI agents, local-first hardware, and biotech integration. The community is moving from "prompt engineering" to "agentic orchestration."

🛠️ Featured Projects

1. NeuroFlow OS

A spatial operating system designed for BCI (Brain-Computer Interface) peripherals. Instead of a mouse or touch, it uses intent-based navigation.

  • The Goal: Reduce the latency between thought and execution.
  • Tech Stack: Rust, WebAssembly, and a proprietary neural-signal processing layer.
  • Current Status:
    • Alpha kernel stability
    • Basic intent mapping
    • Low-latency haptic feedback integration
    • Public Beta API

System Architecture:

2. GreenLedger CO2\text{CO}_2CO2​

A decentralized verification system for carbon capture credits using zero-knowledge proofs to prevent "double-counting" of offsets.

The Math behind the Verification: The system calculates the net sequestration efficiency η\etaη using the following formula: η=∫t0t1(Ccaptured−Cemitted) dtEtotal\eta = \frac{\int_{t_0}^{t_1} (C_{captured} - C_{emitted}) \,dt}{E_{total}}η=Etotal​∫t0​t1​​(Ccaptured​−Cemitted​)dt​ Where EtotalE_{total}Etotal​ represents the total energy expenditure of the capture facility.

3. Synthia: The Local-First Knowledge Graph

A personal AI that lives entirely on your hardware. No cloud, no telemetry, just a local vector database that indexes your entire digital life.

FeatureSynthia (Local)Cloud-AI (Standard)
PrivacyAbsolute\text{Absolute}AbsoluteConditional\text{Conditional}Conditional
Latency<10ms< 10\text{ms}<10ms200ms−2s200\text{ms} - 2\text{s}200ms−2s
Offline ModeNativeLimited/None
CostOne-time HardwareMonthly Subscription

💻 Technical Deep Dives

One user shared a snippet of their new "Lumina" language, designed specifically for asynchronous agent coordination. It looks like a hybrid of TypeScript and Erlang:

// Define an agent with a specific goal
agent ResearchBot {
    capability: [web_search, pdf_parse, synthesis]
    memory: local_vector_store
}

// Orchestrate a multi-agent workflow
async function gatherIntelligence(topic: string) {
    let data = await ResearchBot.execute({
        goal: `Find all papers on ${topic} from 2026`,
        constraint: "Only peer-reviewed sources"
    });
    
    return data.summarize();
}

💬 Community Discussion & Nuance

The thread sparked a heated debate regarding the "Dead Internet Theory." Several developers argued that by late 2026, the majority of web traffic is now agent-to-agent, making traditional SEO obsolete irrelevant.

"We aren't building websites for humans anymore; we are building structured data endpoints for LLM-agents to consume. The 'UI' is now just a fallback for the 5% of users who still browse manually." — User: @bit_shifter

🚩 Common Pitfalls Mentioned:

  • Over-reliance on API credits: Many are switching to Llama-4-Local to avoid bankruptcy.
  • The "Agent Loop" Problem: When two autonomous agents get stuck in a polite loop of "No, you go first," crashing the server.
  • Hardware Bottlenecks: The desperate need for more NPU (Neural Processing Unit) headroom in consumer laptops.

Concept Art: The 2026 Developer Setup


📝 Summary Checklist for Aspiring Founders

If you're starting a project this month, the consensus suggests:

  • Ensure your data is local-first.
  • Build for agents, not just users.
  • Solve a physical world problem (Climate, Bio, Energy).
  • Avoid building another "AI Chatbot."