caleb-brown/temper
1
0
Fork 0
Code Issues 36 Pull requests Projects Releases Packages Wiki Activity Actions

Define repository onboarding and connection lifecycle #38

New issue
Open
opened 2026-07-14 22:37:39 -04:00 by caleb-brown · 0 comments
caleb-brown commented 2026-07-14 22:37:39 -04:00
Owner
Copy link

Parent

#29 — Temper v1 Greenfield Product and Architecture

Question

How should Temper Operators connect a Forgejo host and service identity, choose and install repositories, create or manually configure webhooks, test readiness, rotate or revoke credentials and secrets, recover broken connections, and disconnect or purge a repository while maintaining the intended least-privilege boundary?

Blocked by

  • #31 — Define Temper's trust, authorization, and data-handling policy
  • #32 — Define the supported production deployment envelope
  • #33 — Research the supported Forgejo capability and version envelope

Comments

  • 2026-07-15 — The user chose least-privilege, repository-scoped personal access tokens instead of OAuth for Forgejo access. The remaining lifecycle and UX decisions in this ticket are still open.
## Parent [#29 — Temper v1 Greenfield Product and Architecture](https://git.caleb-brown.dev/caleb-brown/temper/issues/29) ## Question How should Temper Operators connect a Forgejo host and service identity, choose and install repositories, create or manually configure webhooks, test readiness, rotate or revoke credentials and secrets, recover broken connections, and disconnect or purge a repository while maintaining the intended least-privilege boundary? ## Blocked by - [#31](https://git.caleb-brown.dev/caleb-brown/temper/issues/31) — Define Temper's trust, authorization, and data-handling policy - [#32](https://git.caleb-brown.dev/caleb-brown/temper/issues/32) — Define the supported production deployment envelope - [#33](https://git.caleb-brown.dev/caleb-brown/temper/issues/33) — Research the supported Forgejo capability and version envelope ## Comments - 2026-07-15 — The user chose least-privilege, repository-scoped personal access tokens instead of OAuth for Forgejo access. The remaining lifecycle and UX decisions in this ticket are still open.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
dev
t3code/hygiene-review
t3code/configurable-llm-timeout
fix/openai-non-streaming-completions
t3code/test-incorrect-changes
No results found.
Labels
Clear labels   
ready-for-agent
Fully specified and ready for an implementation agent

  
wayfinder:grilling
Human-in-the-loop product or domain decision

  
wayfinder:map
Canonical Wayfinder map

  
wayfinder:prototype
Human-in-the-loop concrete prototype

  
wayfinder:research
Agent-driven primary-source research

  
wayfinder:task
Task that unblocks a Wayfinder decision

No labels
ready-for-agent
wayfinder:grilling
wayfinder:map
wayfinder:prototype
wayfinder:research
wayfinder:task
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks
#40 Prototype Temper Operator workflows and information architecture
caleb-brown/temper
#41 Define the durable domain and audit model
caleb-brown/temper
#42 Define reliability, observability, and recovery behavior
caleb-brown/temper
Depends on
#31 Define Temper's trust, authorization, and data-handling policy
caleb-brown/temper
#32 Define the supported production deployment envelope
caleb-brown/temper
#33 Research the supported Forgejo capability and version envelope
caleb-brown/temper
Reference
caleb-brown/temper#38
No description provided.