inkata

Keep intent connected

I was tired of juggling ticketing systems and knowledge tools. When I gave a coding agent a direction, I wanted that intent to stay connected to the work, not get lost as the agent filled in gaps with assumptions.

That became the starting point for Rinkata, Quirence’s first product. I’m shaping and building it with coding agents, bringing my QA background into the product work. My story goes into that personal transition.

One view, with room to go deeper

I wanted someone opening a project to understand what was happening and how the work connected, without having to dig into every item. They could open a goal, specification, or ticket when they wanted the detail.

Presenting those types of work separately created clutter. My choice was to bring them into one compact view, keeping their relationships visible.

The tension

Show enough context to understand the work without overwhelming the overview.

The choice

Bring goals, specifications, and tickets together, with deeper detail available inside each item.

The reason

Let people see both the work in progress and what it connects to at a glance.

With agents doing much of the work in the background, I also wanted progress to be visible. The meters and bars were part of that intention: people should be able to see the work moving forward.

This is the actual project used to build The Grid, captured on September 9, 2026. It shows the work and its progress at that moment.

In my own use, the combined view has worked well overall. I’m still considering how to reduce the information repeated in the chips, the small labels in the view. That refinement is still open. A useful overview can still have more in it than it needs.

A home for evolving knowledge

Working with coding agents, I kept seeing Markdown documents accumulate inside repositories. Tracking them and keeping them useful became its own job.

I had experienced a similar problem with documentation tools such as Confluence: a document would be written, then go stale as the work moved on. Later, someone else had to recover the context and work out what was still useful.

That led me to give project knowledge one central home in Rinkata. I wanted a place people and agents could return to, with the knowledge updated as the product evolved, instead of leaving the next person to reconstruct it.

Trying it on a real build

Building this site gave me a way to use those ideas together. I wanted dedicated Story and Work pages while keeping the homepage concise. That site-design choice became writing, page composition, and navigation work in Rinkata.

The homepage already had accepted evidence. A successor specification held the new scope while preserving that earlier record.

1. IntentI asked for deeper Story and Work pages.
2. SpecificationThe new direction and its boundaries were recorded.
3. TicketsStory, Work, and navigation became three delivery slices.
4. EvidenceThe result came back with checks and a preview for review.

Put evidence beside the decision

The specification view brings the pieces back together: the three tickets, their pull requests, screenshots, and completion records. I can inspect what was built, rather than rely on a status label alone.

For the Story page, I reviewed and approved the public copy. Its implementation was checked at phone, tablet, and desktop widths, with keyboard navigation, reduced motion, and JavaScript disabled. Those results were recorded with the work. The Work page and shared navigation were tracked separately and later completed too.

What I brought, what I learned

I shaped the connected Work view and the central knowledge direction from problems I had experienced myself. Using Rinkata to build this site gave me a way to keep evaluating those choices against real work.

For The Grid, I supplied the creative direction, background, and copy review. The coding agent translated that direction into implementation, ran checks, and brought back a concrete result. Rinkata held the requirements and delivery evidence.

The lesson from this build is that alignment needs to survive a change of mind. A completed page and a new request can coexist: preserve the evidence of the first, then make the next piece of work explicit. This example shows that trace for one real project; it does not establish a guarantee that agents never drift.

Humans bring the ideas and direction. The work should stay connected to them.

That is the relationship I want Rinkata to support as I keep designing and building it.

Explore Rinkata