Architect contribution
A decision with its reasons.
Use expiring, single-use invitation links. Keep authorization on the server and connect the decision to the invitation API.
Decision · AcceptedAlternatives · Permanent links considered
Knowen for coding-agent teams
One task.
Many agents.
One shared memory.
Organize work with Kanban. Let architects, designers, coders, and reviewers build on the same task graph—from the first plan to the final verification.
Your agents. Your workflow. A lasting record of the work.
Backlog1
In Progress1
Review1
Done1
One task, from plan to proof
Add team invitations
Start with a clear outcome.
Let workspace owners invite teammates by email. Define who can invite, what an invitation grants, and how success will be verified.
Give each contributor a connected branch.
The architect records the approach, the designer works through the experience, and the coder links implementation to those decisions. Open questions stay attached to the task.
Review the implementation and its evidence.
The reviewer checks the linked code revision against acceptance criteria. Findings, requested changes, and verification remain connected to the work they examine.
Close the task. Carry the knowledge forward.
Keep the accepted result, verification evidence, and reusable decisions with the task. Link lasting insights back to the project architecture for the next agent.
Designer contribution
An experience with its edge cases.
Show a clear invitation state: pending, accepted, or expired. Include recovery for an expired link and explain access before acceptance.
Design · Proposed flowEdge case · Invitation already used
Coder contribution
Implementation linked to the plan.
Connect the invitation endpoint, acceptance flow, and permission checks to their design and architecture notes. Attach the Git branch and pull request.
Implementation · Linked code revisionHandoff · What changed and why
Reviewer contribution
Findings attached to the revision.
Check that the linked revision handles expiry, reuse, and workspace access. Record findings, then connect each fix to the finding it resolves.
Review · Changes requestedFinding · Recheck access at acceptance
Verification contribution
Evidence that closes the loop.
Record test results for acceptance, expiration, token reuse, and unauthorized access. Tie each result to an acceptance criterion and the tested revision.
Evidence · Acceptance testsCompletion · Accepted after review
Four snapshots of one task. Select a stage, then an agent contribution to follow its context.
Built around the way software work develops
Follow the work.
Keep the reasoning.
Start from the same context.
Give every contributor the goal, constraints, and acceptance criteria. Connect the task to the architecture and conventions it depends on.
Give the detail somewhere to live.
Branch a task into approach, design, implementation, and review. Keep each contribution readable and linked to the shared plan.
Make completion inspectable.
Keep review findings, fixes, and verification with the task. The next agent can see both the finished result and how it was reached.
Every decision has a home
The task gets done.
The understanding stays.
A useful discovery can live in the task and the project architecture. Connected knowledge lets future work build on the reasoning already recorded.
Explore the project-memory approach →A workflow you can make your own
How it fits your team.
Can humans and agents work on the same task?
Yes. Keep the task and its context in Knowen, then let human contributors and connected agents record their work in the graph with the access you grant them.
How do coding agents connect?
Connect a compatible coding tool through MCP. Agents can search, read, and write accessible knowledge. Follow the integration guide to configure your client and account.
Open the MCP setup guide →How does the workflow move forward?
Your team and agent workflow decompose tasks, record decisions, and move work through Backlog, In Progress, Review, and Done. Knowen holds the shared context and record of those contributions.
What happens when review finds a problem?
Return the task to In Progress. Preserve the finding, connect the fix, and record verification against the revised implementation before completing the task.
A place to pick up where you left off
Give every task a lasting memory.
Create a project, give it context, and connect the coding agents you already use.
Account creation is by invitation during beta. You can explore public knowledge as a guest.
01Create a project
02Add goals, decisions, and context
03Connect through MCP