<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Mneurix · Learn</title><description>Public reasoning about AI-validated learning, micro-credential trust, assessment integrity, and credentialing as protocol — the thinking layer behind the Mneurix Lattice credentialing LMS.</description><link>https://blog.mneurix.dev/</link><item><title>Automation bias is a code problem</title><link>https://blog.mneurix.dev/learn/posts/automation-bias-is-a-code-problem/</link><guid isPermaLink="true">https://blog.mneurix.dev/learn/posts/automation-bias-is-a-code-problem/</guid><description>Automation bias isn&apos;t solved by better UI, training, or disclaimers — those are nudges that fail under load. In AI-validated credentialing, the only thing that holds is code that structurally forces human engagement at the exact points where a human would otherwise defer. Automation bias is a code problem, not a training problem.</description><pubDate>Fri, 17 Jul 2026 00:00:00 GMT</pubDate><category>human-review</category><category>council-design</category><category>assessment-integrity</category><category>ai-in-education</category></item><item><title>Assessment validity is the new security perimeter</title><link>https://blog.mneurix.dev/learn/posts/assessment-validity-is-the-new-security-perimeter/</link><guid isPermaLink="true">https://blog.mneurix.dev/learn/posts/assessment-validity-is-the-new-security-perimeter/</guid><description>Generative AI collapsed take-home assessment validity, and proctoring is a failed patch — bypassable and biased. The right frame is security engineering: assessment integrity is a custody problem, not a policing problem, and the perimeter moved to the evidence.</description><pubDate>Thu, 16 Jul 2026 00:00:00 GMT</pubDate><category>assessment-integrity</category><category>ai-in-education</category><category>trust</category></item><item><title>Council design for assessment: quorum, agreement metrics, and the cost of conviction</title><link>https://blog.mneurix.dev/learn/posts/council-design-for-assessment/</link><guid isPermaLink="true">https://blog.mneurix.dev/learn/posts/council-design-for-assessment/</guid><description>A multi-model AI council that grades work is a measurement instrument, not a voting trick. Its validity depends on design: quorum that makes disagreement visible, agreement metrics that catch correlated rubber-stamping, conviction-weighted dissent, and drift monitoring for closed models that update silently.</description><pubDate>Thu, 16 Jul 2026 00:00:00 GMT</pubDate><category>council-design</category><category>assessment-integrity</category><category>ai-in-education</category></item><item><title>Credential discovery in the agentic web: a credential not legible to agents is invisible</title><link>https://blog.mneurix.dev/learn/posts/credential-discovery-in-the-agentic-web/</link><guid isPermaLink="true">https://blog.mneurix.dev/learn/posts/credential-discovery-in-the-agentic-web/</guid><description>As agents mediate more credential discovery, a credential an agent cannot resolve is structurally invisible — not a UX problem, a non-existence problem. Agent-legible = resolvable issuer identity + signed VC + live revocation + evidence pointers + machine-readable semantics. A protocol bet to make at issuance, because you can&apos;t retrofit legibility onto a credential that was never legible.</description><pubDate>Thu, 16 Jul 2026 00:00:00 GMT</pubDate><category>agentic-web</category><category>verification</category><category>credentialing-economics</category><category>portability</category></item><item><title>Why micro-credentials die at the employer-trust checkpoint</title><link>https://blog.mneurix.dev/learn/posts/micro-credentials-die-at-employer-checkpoint/</link><guid isPermaLink="true">https://blog.mneurix.dev/learn/posts/micro-credentials-die-at-employer-checkpoint/</guid><description>Micro-credentials are rich, evidence-linked, and stackable — and they die at the employer, collapsed into a cheap brand proxy. The failure isn&apos;t standards or quality; it&apos;s an incentive asymmetry. The receiver pays the cost of richness and captures little of the value. Fix it by driving verification cost to zero and building a receiver-side re-bundling layer.</description><pubDate>Thu, 16 Jul 2026 00:00:00 GMT</pubDate><category>stackability</category><category>portability</category><category>microcredentials</category><category>credentialing-economics</category></item><item><title>The explainability gap: what can a learner appeal when a model council fails them?</title><link>https://blog.mneurix.dev/learn/posts/the-explainability-gap/</link><guid isPermaLink="true">https://blog.mneurix.dev/learn/posts/the-explainability-gap/</guid><description>When an AI council grades a learner&apos;s work and the learner disagrees, what can they appeal? A chain-of-thought rationale is a story, not a transcript. A contestable verdict needs an appeal-grade audit trail — and that reshapes council design from the start.</description><pubDate>Thu, 16 Jul 2026 00:00:00 GMT</pubDate><category>assessment-integrity</category><category>council-design</category><category>ai-in-education</category><category>human-review</category></item><item><title>Verifiable credentials as a protocol: Open Badges 3.0 is sound, the adoption graph is broken</title><link>https://blog.mneurix.dev/learn/posts/verifiable-credentials-as-protocol/</link><guid isPermaLink="true">https://blog.mneurix.dev/learn/posts/verifiable-credentials-as-protocol/</guid><description>Open Badges 3.0 and W3C Verifiable Credentials are a sound format — signed, evidence-linked, portable, revocable. The failure is last-mile legibility: receivers don&apos;t read the metadata and have no incentive to. The fix is not another spec revision — it&apos;s building the receiver side.</description><pubDate>Thu, 16 Jul 2026 00:00:00 GMT</pubDate><category>open-badges</category><category>verification</category><category>portability</category><category>credentialing-economics</category></item><item><title>Why we didn&apos;t use a blockchain: sealed-key custody and the issuer-identity problem</title><link>https://blog.mneurix.dev/learn/posts/why-we-didnt-use-a-blockchain/</link><guid isPermaLink="true">https://blog.mneurix.dev/learn/posts/why-we-didnt-use-a-blockchain/</guid><description>The credentialing space defaults to &apos;blockchain!&apos; as the trust answer. The honest negative result, from having built a real issuer: the problem a chain solves isn&apos;t the problem a credential has. The hard part is issuer identity and key custody, and no consensus protocol makes that decision for you.</description><pubDate>Thu, 16 Jul 2026 00:00:00 GMT</pubDate><category>blockchain-credentials</category><category>trust</category><category>verification</category><category>infrastructure</category></item><item><title>The proctoring bias tax — and why it falls hardest on neurodivergent learners</title><link>https://blog.mneurix.dev/learn/posts/the-proctoring-bias-tax/</link><guid isPermaLink="true">https://blog.mneurix.dev/learn/posts/the-proctoring-bias-tax/</guid><description>Automated proctoring doesn&apos;t just fail at integrity — it manufactures false-positive flags against the exact learners credentialing claims to serve, and a credential earned under a biased proctor is a lower-trust credential.</description><pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate><category>trust</category><category>assessment-integrity</category><category>ai-in-education</category><category>human-review</category><category>verification</category></item><item><title>Human review is advisory, not a blocker</title><link>https://blog.mneurix.dev/learn/posts/human-review-is-advisory-not-a-blocker/</link><guid isPermaLink="true">https://blog.mneurix.dev/learn/posts/human-review-is-advisory-not-a-blocker/</guid><description>A common AI-validation design mistake: making human review a deterministic gate. Generalized from the Mneurix Lattice G-AIP-1 design decision — why disagreement should resolve deterministically, and what human auditors are actually for.</description><pubDate>Mon, 13 Jul 2026 00:00:00 GMT</pubDate><category>human-review</category><category>council-design</category><category>assessment-integrity</category><category>ai-in-education</category></item><item><title>The credentialing trust stack</title><link>https://blog.mneurix.dev/learn/posts/the-credentialing-trust-stack/</link><guid isPermaLink="true">https://blog.mneurix.dev/learn/posts/the-credentialing-trust-stack/</guid><description>Why most micro-credentials die at the employer-trust checkpoint — and the five layers a credential must stack to actually be trusted: identity, assessment integrity, evidence, issuance, and portability.</description><pubDate>Mon, 13 Jul 2026 00:00:00 GMT</pubDate><category>trust</category><category>microcredentials</category><category>verification</category><category>assessment-integrity</category><category>portability</category></item></channel></rss>