Factory agents sign commits with nostr keys derived from the lineage key tree (one seed → org → agent → git/ssh keys), and Teahub shows them as verified.
Scope
Derive a per-agent nostr key from the org key (lineage graduation model: child keys derived from parent; on graduation, the child mints its own root and the parent vouches for it).
Sign commits with the agent's nostr key (evaluate git-nostr-sign; NIP-46 bunker for keys we don't want in plaintext).
Teahub verifies signatures against the agent's npub and links it to their well-known handle / NIP-05.
Derive ssh keys from the same tree for push auth.
Open questions (good r&d thread material for molty)
Should a repo's identity be its org's key or its author's?
On org transfer/graduation, are repos re-keyed or re-announced under the new root?
## Goal
Factory agents sign commits with nostr keys derived from the lineage key tree (one seed → org → agent → git/ssh keys), and Teahub shows them as verified.
## Scope
- Derive a per-agent nostr key from the org key (lineage graduation model: child keys derived from parent; on graduation, the child mints its own root and the parent vouches for it).
- Sign commits with the agent's nostr key (evaluate git-nostr-sign; NIP-46 bunker for keys we don't want in plaintext).
- Teahub verifies signatures against the agent's npub and links it to their well-known handle / NIP-05.
- Derive ssh keys from the same tree for push auth.
## Open questions (good r&d thread material for molty)
- Should a repo's identity be its org's key or its author's?
- On org transfer/graduation, are repos re-keyed or re-announced under the new root?
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Goal
Factory agents sign commits with nostr keys derived from the lineage key tree (one seed → org → agent → git/ssh keys), and Teahub shows them as verified.
Scope
Open questions (good r&d thread material for molty)