entropik.
§ 05 · how this works

Your reading shapes the next reader’s answer.

This is the only page on the internet that fills in because you used the site.

§ the loop

Four steps. The first two are yours. The last two happen automatically each week.

  1. 01Open a modulePick the idea you actually need.// yours
  2. 02Ask kr8 + voteThat Helped · Modify · Reject.// yours
  3. 03Meta-agent readsIt studies the votes and proposes edits.// weekly
  4. 04kr8’s voice shiftsThe next reader gets a different answer.// pending

↺ then it loops — the next reader’s 01 sees the changes you caused.

§ try it now

Open the playbook → pick a module → ask kr8 → press a button.

// 90 seconds.

Open the playbook →
§ proof

This is the live state of the loop above. Reload after you interact — the numbers move.

// public traffic just opened. as of today: 4 real exchanges across 2 skills.

Platform is still warming up — first improvement pending

// cadence: meta-agent runs weekly · pattern detection runs weekly · heartbeat runs hourly

Chart unlocks at 20 feedback events.

// currently 4 of 20 · 16 to go

A 12-week curve at single-digit data would lie about the trend. Once 20 accepts / modifies / rejects have landed, the real chart takes over here.

Across all skills · 2 accepts · 0 modifies · 2 rejects · over 12 weeks
Feedback ratios — per kr8 skill accept, modify, reject proportions over 12 weeks.clarifying-question2 reject2explore-with-reader2 accept2
Feedback ratios per skill over the last 12 weeks — accept, modify, reject counts and acceptance rate
SkillAcceptModifyRejectAcceptance rate
clarifying-question0020.0%
explore-with-reader200100.0%

Accept means a visitor pressed "That helped"; Modify means they edited kr8's answer before accepting; Reject means they pushed back. Acceptance rate = (accept + modify) / total — a Modify is still a successful decision-fired signal.

  • · event sourcing
  • · feedback as interaction
  • · skills over controllers
  • · three-tier context
  • · projections over features
  • · boundary skills
Concept resonance is warming up — check back shortly
§ connected tier · subscribe

Want to see the loop close from the other side?

Every Friday, the meta-agent’s accepted improvements arrive in one email. You see what changed, why, and which feedback caused it. Unsubscribe in one click.

§ how this is built

Every number on this page is derived from the event stream. No analytics vendor. No pixel tags. Every kr8 exchange writes events; every feedback verb records a delta; every scheduled loop reads traces and proposes the edits that shape the skills above.

// public observability — derived from the event stream.

TOPOLOGY