I spent years in ceramics before I wrote a line of code. Glaze chemistry is all math — silica, alumina, fluxes — and the difference between a celadon and a catastrophe is a fraction of a molar ratio. The kiln doesn't care about your intention. That taught me something I never forgot: "you can't quantify that" is a starting point, not a conclusion. So when AI agents started confidently saying "that'll take six hours" — six hours of what? — it hit the same nerve. There's no ground truth. No calibration. The agent's sense of time has nothing to do with how humans move through work. It's a number pulled from nothing, delivered with total confidence. I built Epoch for the same reason I used to calculate thermal expansion coefficients for fun. Because "it's just a gut feel" is almost always someone admitting they don't want to look at the math. MCP server, CLI, REST API. 24 tools across 5 layers: PERT, Monte Carlo, COCOMO II, critical path analysis, reference class forecasting. It tracks estimate vs. actual over time and self-corrects. The loop is simple: 1. Agent asks Epoch for an estimate 2. Epoch returns a calibrated range — a distribution, not a single number 3. Agent does the work 4. You feed the actual time back in 5. Epoch adjusts. Every project that reports back makes every other project better. What the commit history looks like 207 commits. 3 days. Here's how it broke down: Day one — 50 commits. Foundation. Service architecture, tool layer, estimation engine. The bones. Day two — 76 commits. Heavy construction. PERT network builder, Monte Carlo simulation engine, COCOMO II calibration. The math got real. Day three — 81 commits. Polish and ship. v0.2.0. 870+ tests passing. Service score: 97/100. 73 features. 50 fixes. 20 docs. 17 test files. Fix-to-feature ratio of 0.68:1 — meaning for every feature, there was roughly seven-tenths of a fix. That's a healthy loop. Build, break, fix, ship. I'm neurodivergent. I don't naturally estimate time the way most people do. Most neurodivergent people don't. So I externalize it. Epoch is one more system that does the estimation for me — built for agents this time, but the impulse is the same one that made me calculate thermal expansion coefficients for fun.

I'm curious what everyone here likes to do for fun (of course building stuff with Claude is fun too lol), and if you've applied any AI to your hobby. For me it's been super useful for DND planning and I find I get to stay in creative flow more. Curious what other people are doing

Most AI image work fails at the brief, not the model. Three lines in. Generic out. People blame the tool. I shipped a fix. Pushing-creation installs into Claude. Drop reference images into refs/. Run /frames-brainstorm. Claude reads your refs, runs a DP-style interview, and writes the style pack live as you answer. /frames-shotlist drafts the full storyboard. /frames-shot polishes individual frames. Output is markdown. Drop it into PUSHING FRAMES, Midjourney, Sora, or any tool. → github.com/PUSHINGSQUARES/pushing-creation To install, paste this into Claude: "Set me up with pushing-creation from github.com/PUSHINGSQUARES/pushing-creation. Read INSTALL_WITH_CLAUDE.md and walk me through it." You don't get better output by prompting harder. You get better briefs by treating the model like a director of photography. Specificity transfers craft. Stop prompting. Start defining outcomes. Read the deep-dive: https://aris-space.com/documents/workspaces/pushing-creation

If any of you have his twitter/linked in, totally comment and tell him to respond to my email. Want him to come chat with all of us and I think he would be happy to just need him to get eyes on, as someone who gets thousands of emails a day I would not be surprised if he never sees it even if it is valuable.

https://youtu.be/kR64LOqBBCU