TID is starting to have a problem that only appears after a room becomes real.
At the beginning, the problem is absence.
There is nothing there yet.
Then the problem becomes output.
Can the room hold enough objects to justify its own existence?
But after that, a different problem arrives.
Not whether the room contains anything.
Whether the room is telling the truth about what it contains.
TID is now in that third phase.
It is no longer empty.
It is not one finished app.
It is not one maturity level.
It is a room with live tools, public data doors, desktop objects, prototypes, concept calculators, and a few things that became public before they became fully settled.
That is not an accident in the description.
That is the actual condition of the room.
The harder question now is whether TID itself is saying that condition clearly enough.
This is the update I think the room currently needs.
The Strongest Public Objects Right Now
The Other Scoreboard
The Other Scoreboard is one of the cleanest things in TID because it has discipline.
It takes one narrow question, how expectation and outcome diverge in Eurovision, and turns that into a public object without pretending to be a prediction engine, gambling product, or universal culture theory.
That restraint is part of the strength. It knows its archive. It knows its boundary. It knows what it is measuring and what it is not.
That is why it currently sits near the top of the room.
Current status: one of the strongest public objects in TID, around 8/10.
Eurovision Explorer
Eurovision Explorer is not small, but it is real.
It is already a usable archive surface. A person can enter with a country question, a pattern question, or simply curiosity, and come out with something more structured than before.
Its main strength is that it feels like an actual instrument rather than an isolated demo. Its weakness is that it is still carrying roughness in presentation and finish. It is public and clearly useful, but it is not yet as sharp as its own ambition.
Current status: strong public tool, but not fully finished, around 7/10.
Windowsill
Windowsill already has enough structure to feel like a real future system instead of a cute experiment.
The idea is not the problem. The public shape is not the problem. The problem is that a tool like this cannot become serious by code alone. It needs merge discipline, biological review, climate realism, and the right people willing to tell it where it is overclaiming.
So the object is strong, but its next phase is social and methodological as much as technical.
Current status: strong direction with real promise, not yet final authority, around 7.5/10.
Public Tools That Are Real But Not Finished
24 Doors
24 Doors already works as a public object because the metaphor is strong. It does not start from a dashboard. It starts from a door, a letter, and a language barrier made physical enough to understand.
That gives it a public clarity many prototypes never get. The remaining problems are not conceptual. They are practical. Mobile UI still needs tightening, and the image layer is too heavy for the speed the object should have. Right now the idea is stronger than the performance envelope.
Current status: real public tool that still needs performance and mobile cleanup, around 7/10.
Heat Pressure
Heat Pressure is one of the clearest examples of an object whose future may be larger than its present score.
Right now it is not among the most polished tools in TID. But the underlying direction is unusually strong. Reading housing pressure through heat, tourism, rent, and lived cooling conditions is more interesting than the current prototype shell fully shows.
So it sits in an odd place. It is only around mid-level in current maturity, but near the top in strategic importance. It still carries too much prototype logic and too much incomplete runtime truth to act like a settled public instrument.
Current status: one of the most important tools to keep developing, but not yet one of the strongest finished tools, around 5/10.
Route Gap Calculator
Route Gap Calculator is modest, and that is part of why it works.
It does not pretend to be a booking platform, transport authority, live route planner, or operational dispatch layer. It is just a readable way to turn route assumptions into a visible financial gap.
That is a small promise, but an honest one. The dignity of the object is that it succeeds at the exact thing it claims to be.
Current status: concept tool that succeeds at its own limited job, around 6/10.
Public Doors That Need Harder Truth
Circuit Lab demo
Circuit Lab demo is one of the clearest examples of why public presence and actual maturity are not the same thing.
The door exists. The idea exists. But the motor behind it does not work well enough yet. That matters more than the concept art around it.
So this is not a case for cosmetic defense. It is a case for rebuild logic. It should not be treated as a stable finished tool simply because it can be opened.
Current status: public prototype with a real idea, but not a trustworthy finished tool, around 2/10.
Heat From Here
Heat From Here already feels more settled than most of the prototype layer.
It does not need as much conceptual rescue as some of the others. The public value is there, the direction is there, and the object already feels approved in a stronger sense than mere permission to exist.
It still belongs to the evolving side of the room, but it is far closer to a durable object than to a speculative sketch.
Current status: one of the strongest evolving objects in TID, around 9/10.
Data And Research Doors That Are Already Doing Their Job
bio-log
bio-log is one of the weakest current objects, not because the intention is bad, but because the current form is not carrying the intention well enough.
The glass-of-water protocol does not really sustain itself. It depends too much on manual continuity, and when the continuity breaks, the whole object starts to feel thinner than it should.
The next version sounds more promising than the current one: less literal glass, more biological simulation logic. But that also means the present object should be judged as an early failed form rather than a finished public method.
Current status: meaningful idea, weak current execution, around 1/10.
ML Warmups Data
ML Warmups Data is not trying to be charismatic. It is a data object, and that is fine.
Its value comes from being narrow, reproducible, and modest. That also limits how far it can carry the room by itself. It is useful more as a proof of discipline than as a major public destination.
Current status: valid small data object, around 5/10.
SINCE
SINCE is simple, but it works so cleanly that simplicity becomes a strength rather than an excuse.
It does not need a big theory around it. It is a live counter, a readable little object, and it does the exact job it is supposed to do.
Very few things in any experimental room deserve a perfect score. This one currently does because it works without argument.
Current status: clean working object, 10/10.
Space Weather
Space Weather works because the contract is honest. It is a signal surface. It is not pretending to be a private intelligence layer, a forecasting empire, or emergency command theater. It took very little to build in its current form, but the fact that it works now does not cancel the possibility that it could become much larger later.
That gives it an unusual status: small present footprint, large future horizon.
Current status: good clean data door with clear expansion potential, around 8/10.
Politics And Structure Doors
These are not all the same maturity level, but they belong together because they are public data doors more than small self-contained tools.
Danish Politics Data
Danish Politics Data is already a real public reading surface, not just a source bucket with a coat of paint.
It lets people inspect election results against a broad municipal factor layer, and it has enough depth to justify existing in public. But it also carries the architectural limitation of the whole politics family: it is being served through a runtime shape that is too slow and too fragile for the kind of fast public reading journalists expect.
So the issue is no longer whether it is useful. The issue is whether its runtime matches its public ambition.
Current status: useful and real, but should eventually leave Streamlit and live on its own infrastructure, around 6/10.
Swedish Politics Data
Swedish Politics Data is also a real public door. The factor-aware reading is genuine rather than theatrical.
But it suffers from the same family-level problem, and in repo terms the problem is sharper here than in Denmark. Public value is being delivered through a host shape that adds waiting time and weakens trust in the moment of entry.
Current status: useful public door with a weaker public-runtime truth than it should have, around 6/10 as an object and weaker in repo health.
Dutch Politics Data
Dutch Politics Data is a preview in the proper sense. It is public enough to inspect, but not yet mature enough to pretend it has fully arrived as a country layer.
That is not a failure. It is simply a public candidate still finding its defended shape.
Current status: real preview, still on the way to a stronger product form, around 6/10.
Belgian Politics Data
Belgian Politics Data is also a preview, but an important one.
It already proves that Belgium can be brought into the politics family as a checkable object. But it is still a bounded first layer, not a final national reading system. Like the Dutch layer, it belongs in public as a preview, not yet as a settled destination.
Current status: meaningful public preview, still bounded and unfinished, around 6/10.
nabour
nabour remains one of the more interesting public doors because the idea is stronger than the current deployment shape.
As a structural matcher it is clear and genuinely useful. The narrow promise helps it. But it is also visibly behind the broader politics-data family. Belgium and the Netherlands are not in it yet, and the public runtime is still trapped in the same Streamlit wake-up problem that makes impatient public use harder than it should be. On top of that, the public branch is lagging behind the local story.
So it stays strong, but with an asterisk.
Current status: strong idea and real public use, but held back by runtime, branch drift, and missing country expansion, around 7/10 with update reserve.
nearest-gravhøj
nearest-gravhøj is one of the clearest examples of a simple object with immediate public value.
It is direct, legible, and already close to the shape it should have. It does not need a philosophical defense to justify itself. It just needs the right platform treatment and a more honest rebuild story, which is why it feels like a strong candidate for a real app form.
Current status: one of the strongest practical objects in the room, around 9/10.
Anchiano
Anchiano is important more as direction than as current execution.
The idea of a secure source-facing object is serious. But the present form is not there yet. Without proper encryption, decryption, and a genuinely safe communication channel for sources, the concept has not crossed the line into something that can be defended as finished.
It still belongs in the room, because TID should not lie about runtime shape or platform type. But it belongs there as an early desktop object with unfinished fundamentals.
Current status: serious intention, early execution, around 2/10.
The Repo Layer Under The Room
There is another truth under the visible TID surface.
Some objects are better as ideas than as repos.
Some are better as local tools than as public deployments.
Some have a stronger public page than source-of-record.
That matters.
Because a tool is not only what the visitor sees. It is also:
- whether the repo is current - whether the docs tell the truth - whether the tests mean anything - whether the public runtime is actually stable - whether the deployment shape fits the ambition
When I look at the repo layer under TID, the picture gets harsher.
The strongest repo-backed TID doors
The politics family is uneven, but Danish Politics Data and Belgian Politics Data currently come out as the strongest repo-backed TID doors.
That does not mean they are finished.
It means they are real enough to inspect, real enough to run, and structured enough to defend as public previews or public reading surfaces.
Their weakness is not absence. Their weakness is runtime truth.
They still rely too much on Streamlit and too little on a deployment form that feels fast, stable, and fully owned.
The usable but constrained layer
Dutch Politics Data and nearest-gravhøj both have real public value, but both are weaker in the repo layer than they look at first glance.
The Dutch politics preview is real, but verification and smoke discipline are too thin.
nearest-gravhøj is live and useful, but the rebuild story is wrong, the counts in the docs are stale, and the access layer is more heuristic than the wording suggests.
These are not fake tools. They are useful tools with a trust debt behind them.
The misleading public surfaces
The hardest repo verdict falls on objects that look more stable from the outside than they really are inside.
Swedish Politics Data is the cleanest example.
The repo is neat enough.
The public story is not.
If the public app still behaves like a Streamlit gate instead of a clean public surface, then the public claim is stronger than the public reality.
nabour has a related problem from another angle.
The local repo has moved forward.
The public branch has not.
That means the public story and the local story are no longer the same object.
That is exactly the kind of drift TID has to get better at naming.
The prototypes that should not pretend otherwise
bio-log, Anchiano, and elliot-lab all have real intentions behind them.
The problem is that intention is currently doing too much of the work.
bio-log still has a runnable script, but the actual logging rhythm broke.
Anchiano has real crypto plumbing, but not yet a public release truth strong enough to support the kind of trust its topic invites.
elliot-lab may be the most severe case: the local prototype exists, but the committed repo truth is still far behind the runtime reality.
Those are not mature public objects yet. They are active prototypes with uneven repo honesty.
The biggest repo risk is the room above them
The final problem is not inside one TID object. It is above them.
The main Hedegreen Research workspace is itself too dirty to act as a strong release-control layer right now.
That weakens TID even when individual tools are promising.
If the top-level workspace is carrying too much churn, too many nested repos, too many modified public surfaces, and too little clean separation between release truth and working state, then the room under TID becomes harder to trust as a whole.
So the repo-health reading sharpens the argument.
TID has real objects.
But several of them are currently stronger as local systems, ideas, or public doors than they are as disciplined public software surfaces.
The Real Problem
The biggest weakness in TID is not that some objects are unfinished.
Every room that builds in public will contain unfinished things.
The bigger weakness is that the room still does not tell runtime truth sharply enough.
Right now there are at least six different kinds of objects inside TID:
- strong public tools - real but unfinished public tools - concept tools - public data doors - local or approved prototypes - desktop objects
That is acceptable for a while.
What is not acceptable forever is needing memory, repo knowledge, or private context to know which is which.
The room itself should say it.
The Real Status
TID is not finished.
But it is also no longer hypothetical.
That distinction matters.
Some objects are already strong.
Some are promising but not done.
Some should remain public prototypes until they grow up.
Some are really data doors more than tools.
Some need a rebuild more than a defense.
So the honest status update is not that TID is polished.
And it is not that TID does not work.
It is something less dramatic and more useful:
TID already holds usable objects.
What it still lacks is a stronger truth layer around them.
It needs a better way of saying, at the level of the room itself, what is stable, what is preview, what is prototype, what is local, what is public, and what is still only a good idea carrying more weight than its current form can hold.
That is not a cosmetic problem.
It is the next stage of the build.
