TSC Public Reports

The Shadow of Organizational Trauma

The committee's dysfunction stems from a foundational trauma that permeates every meeting. On October 15, 2025, Neil Davies provided the most direct articulation:

"The Intersect and Mr. Hoskinson has emasculated the behavior of the TSC and everything we've tried to do has been shot down in flames. Basically, why do they feel motivated to do this work? That's your basic problem — the context in which the TSC is operating is it has no resources, it had its remit changed about it from the outside world, and a lot of people basically are thinking there's nothing to push forward here. That's why people are not standing for election."

This trauma resurfaces when Udai Solanki suggests the TSC should drive major technical initiatives on December 10, 2025. Neil responds: "Unfortunately, that is precisely what we got shot down in flames for doing and people lost their jobs and their companies got it excluded from the whole ecosystem for trying to do."

Sebastian Nagel clarifies: "The budget thing which was shot down was not that the TSC has an own budget to do TSC stuff. It was more about the remit of the TSC being involved on the bigger intersect treasury budget proposal process in steering that in a technical sound direction."

This past rejection has created a culture of learned helplessness where committee members actively avoid leadership and retreat into ever-narrower scopes of activity. The six-month Vice Chair vacancy is not an administrative failure — it is a symptom of members refusing to take ownership of an institution they believe will punish them for exercising authority.

Leadership Vacuum and Procedural Paralysis

The committee's inability to fill basic leadership positions reveals deep demoralization:

• October 15: Terence McCutcheon asks about chair nominations. No volunteers emerge except Kevin Hammond's willingness to continue.
• November 26: Neil Davies attempts to formalize the process but discussion devolves into procedural delays.
• December 3: Alexander Moser forces the issue: "Can we just agree that Kevin is chair and remove it from next week's agenda? Can I make the motion to elect Kevin as chair, the only one that put himself forward? Let's get it over with."
• March 25: Vice Chair position still unfilled after six months of repeated pleas.

This pattern reveals a committee so demoralized that members actively avoid taking responsibility for its direction.

Constitutional Crisis: A Case Study in Powerlessness

The handling of Constitution v2.4 represents the committee's most egregious governance failure. On January 21, 2026, Kevin Hammond reveals: "Apparently the civics committee was not aware either or some of the reviewers. So there's a serious disruption in the flow."

The committee discovered that guardrail labels had been reused, breaking automation. Kevin notes on February 18: "every guardrail has been broken by this change because the text has been changed in all the guardrails."

Neil Davies' response on February 25 captures the frustration:

"I'd like to know why you can justify that position. Sorry to be vicious, but say something to me. Is this actually something that we care about? I mean, do we care about Cardano? Because if the Constitution is a mess, we got to do something to fix it, right?"

Yet when pushed to act, committee members retreated into jurisdictional debates about whether reviewing the constitution was within their remit. Nicolas Biri argued: "It's far beyond our remit... I'm really uncomfortable with it." Kevin countered: "I believe that there should have been a technical and a legal constitutional review of the constitution before it was put on chain." The committee could not agree on whether fixing a broken constitution was its job.

Budget Allocation: Theater of the Absurd

The March 2026 budget discussions expose fundamental dysfunction:

Misaligned templates: The committee was forced to fit technical governance work into product development "pillars." Nicolas Biri's response on March 11: "I try to understand the rational of aligning the TSC work with the product committee pillars. It sounds very weird to me... I wouldn't say stupid but yes I will say stupid."

AI-generated submissions: Kevin Hammond admits on March 18: "I have become friends with AI over the last few days" to complete budget templates within a 9-day deadline. The technical governance of a multi-billion dollar blockchain ecosystem was documented using AI-generated text because the committee lacked time and resources for proper preparation.

Insulting valuations: The committee proposed $150 payments for reviewing multi-million dollar technical proposals. Neil Davies explodes on March 25:

"If you're going to review a two or three or $5 million project... to say you can do that for $150 is absolutely bloody laughable... people will look at this and just say they're playing... it's absolutely bloody laughable."

Information Control and External Dependencies

The committee faces systematic information asymmetry:

Communication infrastructure collapse: On November 26, Kevin reports: "as of 12:30 today UK time all IO members... who's using the IO slack to access this now no longer has access... we have lost a means of communicating with several of our TSC members." The committee's communication channels depend on external entities that can revoke access unilaterally.

Technical surprises: Neil Davies expresses frustration about Plutus parameter changes on December 3: "given what's happened in past cost models and how they have been sprung on us... I just don't want to be in that position of having to do that in a 48 hours before it gets voted on." The committee responsible for technical oversight is routinely surprised by technical changes.

Access barriers: Hard fork information remains behind Intersect membership walls, as Sebastian Nagel notes on March 11, creating artificial barriers to technical participation.

Parameter visibility failure: On March 25, Neil asks members to indicate if they'd seen a critical parameter update: "Could you raise your hand or put a thumbs up or something if you've already seen it? That was just Kevin. Nobody else." Neil's conclusion: "There in lies a problem, gents. This shouldn't be new news to you."

IOG's Shadow Governance

Despite formal independence, IOG maintains effective control over Cardano's technical direction:

Technical decisions: On March 25, Bosko states about the node release: "it's not something we can directly influence through TSC... It's the way the big piece of work will happen after this thing is after the node is pre-released." The committee responsible for technical steering cannot influence the most critical technical deliverable.

Information flow: Duncan Coutts consistently serves as the conduit for IOG positions, while other IOG members remain notably silent during contentious discussions.

Resource dependencies: Critical technical work depends on IOG funding decisions, as seen with CIP editor positions funded only through March 2026. Sebastian Nagel raised alarm: CIP editors were "having struggles getting funded through Catalyst" and seeking "different ways of getting their work funded."

Security Theater vs. Security Reality

The committee's approach to security reveals dangerous gaps:

Chain partition incident (November 26): Report delayed by board review, prompting Neil Davies to censure the board on January 14: "I wish to censure the board for changing the terms and conditions of the committee after it was agreed at the beginning." A security report that should have been published promptly was held up by governance politics.

Security officer appointment: Mike Hornan appointed as Security Incident Response Officer (January 14) with celebration but no discussion of resources, authority, or process.

Information withholding: SPOs told to trust security updates without details (raised by Leandros on March 4).

Cultural Dynamics: Passive-Aggressive Politeness

The transcripts reveal a culture where serious concerns are immediately softened. After extensive criticism of the Cardano Foundation on December 3, Kevin Hammond follows with: "I do want to say thank you to Christian and the team... I don't think there's any criticism there." This pattern — sharp technical critique immediately followed by relationship smoothing — suggests maintaining interpersonal harmony takes precedence over resolving technical disputes.

Perpetual Process Without Progress

Three topics appear in every meeting without resolution:

1. Vice Chair election: Six months of pleas, zero volunteers
2. Hard fork timing: Every meeting includes vague Q1/Q2 estimates that slip continuously, from January 2026 to "beginning of June"
3. Parameter committee coordination: Fundamental questions about authority remain unresolved throughout the series