Clarity School is available now. Building the next generation of Clarity around connected context and the next useful action.
Audecius CEO @MoritzZinecker
Audecius Open can be inspected without an account.
CSV, JSON and a REST API are public under CC BY 4.0. No key. No sign-up. The schema, sources, confidence labels and citation travel with the access route.
Open data becomes stronger when people can disagree with it precisely.
Audecius Open publishes CSV, JSON, a REST API, sources, confidence labels, missing values and a version DOI so feedback can point to a record—not just a brand claim.
Five school-year-start entries in Audecius Open have no date.
They concern Baden-Württemberg and Bavaria. The empty values are published as empty values. A plausible estimate would still be an invented claim.
A subject is context. Homework is a specific obligation. A project develops across several steps. Clarity School currently keeps those schoolwork objects available inside the same app.
A low-consequence suggestion and a high-consequence decision should not share the same confirmation flow. Audecius documents that distinction as design work for Ariadne.
Before adding another school notification, ask who needs to act, what changed, and whether the recipient can respond. Information without a clear hand-off becomes noise.
You do not have to adopt an entire system on day one. Clarity School is currently available on iPhone and iPad; one calendar view, one homework item, or one focus session is a valid place to begin.
A five-minute school reset: collect loose tasks, check the next deadline, choose one first action, and leave one buffer. The goal is not a fixed plan; it is a plan you can revise.
An exchange student needs a different hand-off from a generic school calendar.
Audecius Open marks 69 entries for exchange students. The intended role travels with the date, confidence and source.
North Rhine-Westphalia begins its 2027 summer holidays on 19 July. Baden-Württemberg begins on 29 July.
Both sit inside a 35-day national span whose state dates are all marked official in Audecius Open.
Smooth software should not hide a consequential decision.
The person affected needs to see the action before it matters, understand what changes and decide when review is required.
Accessibility is a product property. Conformance is an evidence claim.
Clarity documents scalable text, keyboard access, visible focus, reduced motion, VoiceOver metadata and system contrast—while withholding a formal WCAG claim until full testing exists.
@TeachHub One thing that reliably lowers the stress: a single printed handout with the week's routine, how to reach you, and where homework is posted. Parents stop asking the same three questions and the evening runs shorter.
@jmattmiller The "enhance an existing lesson" framing is the useful one. Starting from a lesson that already works and asking for one variation (a retrieval quiz, a misconception check) is far less overwhelming than generating from scratch.
We are exploring transcription as a possible capture input—not announcing it as a current Clarity School feature.
The design question: when a transcript is wrong, what is the fastest correction path you would trust?
A school planner should make the next decision easier without making it for the student.
The useful question is not “How full is the schedule?” It is “Can I see what competes for my time—and change the plan?”
@jasonfried Voice works best when it maps to explicit, reversible actions. “Move this to Reply Later” is safer and clearer than “handle my inbox”—especially when the system reads back the action before anything is sent.
@rauchg Zero-setup tools remove friction, but they also move the trust boundary. A useful gateway should make four things legible before an agent acts: what the tool can read, what it can send, what it costs, and where approval is required.
@supabase Inheriting existing scopes is the right default. The next test is whether every AI action is attributable to the human, role, and policy snapshot that authorized it—so a later review can explain not only what changed, but why access existed at that moment.
@FLI_org A tracker becomes much more useful when it records not only what happened, but which control surface failed: what the agent could do, who could interrupt it, what evidence was logged, and how recovery worked. Capability without reversibility is the wrong progress metric.