40 lines
1.5 KiB
Markdown
40 lines
1.5 KiB
Markdown
# PR#88: The Spike of T3 Code Gets Five Checks and Two Decisions
|
|
|
|
Version: patch
|
|
|
|
> **WARNING:** This document describes only the change applied in this PR.
|
|
> It may already be outdated once the next PR is merged.
|
|
> Historic PR documentation is not maintained along with new PRs; treat it as a snapshot.
|
|
|
|
## Related Links
|
|
|
|
- [werkregie PR#87](https://git.javagil.de/mi/werkregie/pulls/87), which planned the spike `#sat.t3`.
|
|
|
|
## Problem
|
|
|
|
The plan of werkregie PR#87 leaves five questions about T3 Code open:
|
|
|
|
- Does T3 Code work with Gitea?
|
|
- Can a satellite log in to Claude without access to the user's whole account?
|
|
- Does Claude Code under T3 Code load the memory, `CLAUDE.md` and the skills?
|
|
- Can the client open a dev server that an agent starts on a satellite?
|
|
- Can a satellite be another Unix user on the same machine?
|
|
|
|
The user also made two decisions that the plan does not hold yet:
|
|
Werkregie does not take over the functions of T3 Code, and a customer who needs isolation provides the Claude login.
|
|
The spike must also evaluate whether Werkregie can reach all its agents through T3 Code only.
|
|
|
|
## Non-Goals
|
|
|
|
- No code; the plan only.
|
|
|
|
## Solution
|
|
|
|
- `doc/werkregie.werkbaum`, node `#sat.t3`: the goal of the spike, five new steps, and the decision of the user as `[x]`.
|
|
- `#sat.isolation` is decided: a customer who needs isolation provides the Claude login; otherwise the user's own.
|
|
- Block `#sat.t3`: the decision and the findings from the documents of T3 Code.
|
|
|
|
## Open Questions
|
|
|
|
None.
|