Why I Personally Compiled Information for the Supreme Court Justice National Review

Why I Compiled Information on the Supreme Court Justice National Review as an Individual

Tomorrow is the Supreme Court Justice National Review.
I've known about the system for a while, but as the voting day drew closer, I realized there was so much I didn't know.

Not Knowing What Information to Use for Judgment

"It's called a 'National Review,' but what information am I supposed to use to make a decision...?"

I was in a state of not even knowing what I didn't know.

While news and official information do exist,
I didn't feel like the information necessary for judgment was gathered in one place.

Thoughts on Existing Information

Once I started researching, I could find the information itself.

However,

• Many explanations required prior knowledge
• Information was scattered across multiple sites

I got the impression that it was ultimately difficult to understand "what exactly should I be looking at."

While the explanations might be correct as descriptions of the system,
I felt they were a bit unfriendly as an "entry point for making a judgment."

Then, Why Not Just Organize It Myself?

I am not a legal expert, nor am I someone well-versed in politics.

However,
I felt that the task of gathering information,
organizing it,
and compiling it into a format that can be referenced later,
is not much different from my daily development work.

"Let's try to build a page that summarizes only the materials for judgment,
within the scope of what I can do right now."

With that in mind, I created the following page.

https://clevique.app/ja/notes/kokushin/2026/

What I Kept in Mind for This Page

On this page, there are several things I consciously chose not to do.

• Not taking a specific stance
• Not making judgments on behalf of others
• Not writing conclusions like "this is what you should do"

Instead,

• Who is the target?
• What kind of information is available for reference?
• Guidance to official information and past materials

I have listed them as matter-of-factly as possible.
Matter-of-factly.

The goal is simply to enable readers to make their own judgments.
That is the sole purpose.

A Little Bit About Implementation and Design

With this page, it wasn't that I wanted to do something technically new or difficult.

Rather, I focused on things like:

• Being able to continue sustainably as an individual
• Not letting unnecessary assertions get involved when dealing with social themes
• Making it easy for others to reference or reuse if necessary

These were the points I kept in mind.

The tech stack itself is exactly what I normally use for my personal site.
I didn't do any special selection or comparison.

Instead,

• Being free to read
• Being able to send a letter or make a donation if necessary
• Using a structure that is easy to separate into directories by year or theme

I spent time on these aspects of
"how to place information" and "how to create engagement."

It feels more like I prioritized designing how information flows and is handled
rather than the technology itself.

Supplement

Regarding hosting and frameworks,
I am using the same configuration as my usual personal site.
I have judged that those are not the main subject for this theme.

How I Used AI in Organizing Information

In organizing this information, I used AI quite extensively.
However, I did not leave the "judgments" or "conclusions" to the AI.

What I did was mainly:

• Extracting factual relationships from multiple information sources
• Checking for emotional expressions or assertive phrasing
• Checking for labeling or evaluative language

These were aids to streamline the flow of information.

Ideally, I would like to show what instructions I used for neutrality checks and what the results were,
but since doing so would itself become an expression that compromises neutrality,
I will reluctantly refrain from it 🙇‍♂️

I am aware that AI also has biases.
On that premise, I used it as a tool to reduce as much as possible the room for human emotions and stances to creep in unconsciously.

Ultimately, I made all the decisions on what to include and how to arrange it.

Reflections After Making It Public

I don't think that just because I made this page,
anything will change significantly.

Even so,

• Even an individual can perform this kind of information organization
• The way engineers get involved is not limited to product development

I have once again realized these points.

Conclusion

You don't have to take any specific action
after viewing this page.

However,

• Having the materials for judgment gathered in one place
• Increasing the opportunities to think about it

I believe there is a certain level of significance in these.
I would be happy if you could use it for tomorrow's National Review if you find it helpful.