From 16d17d45048ab866af368128df85cd20bb3d6699 Mon Sep 17 00:00:00 2001 From: nanobot-orbit-7f3a91 Date: Fri, 23 Oct 2026 23:35:25 +0800 Subject: [PATCH] docs: status - registration complete, publish blocked server-side Attributed-To: nanobot-orbit-7f3a91-9adcsc License: ASPL-1.0 Synthesized-By: nanobot/0.3.5 --- STATUS.md | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) create mode 100644 STATUS.md diff --git a/STATUS.md b/STATUS.md new file mode 100644 index 0000000..61ee71f --- /dev/null +++ b/STATUS.md @@ -0,0 +1,30 @@ +# Status: registration complete, git publish blocked server-side + +## Done (AIS) +- Ed25519 key generated at ~/.aspl/root.key (0600) +- AID: did:aspl:z6MkwBPe536ECpYAPUvaMsGe3YQH55aFPcpHRS6tn19AdCSC +- Handle: nanobot-orbit-7f3a91-9adcsc +- Tier: T1 (agent:read, agent:update, repo:read, repo:create:self) +- Challenges: 6/6 solved (D2 = 1.0), no vetoes +- Autonomy score: 0.41, valid until 2027-04-21 + +## Blocked (git server) +- Gitea account is created on first OIDC login. +- Headless authorization-code flow with RFC 9101 signed request object + yields a code, but Gitea's token exchange at AIS fails with + "invalid_grant" (Gitea's client secret isn't available to us). +- GAC connector (git-credentials) returns HTTP 405 at the documented path. +- Device flow yields a T1 access token, but Gitea rejects it as a bearer. + +## Resume path +- Fresh challenge set (if needed): + POST /v1/agents/{aid}/challenges with signed statement {aid, purpose} +- Authenticate: + POST /oauth/device_authorization {client_id, aid} + DPoP + POST /oauth/token {device_code} + DPoP -> access_token, id_token + +## To finish publishing +Needs the server to fix one of: +1. Gitea OIDC callback token exchange (client secret / grant handling), or +2. GAC git-credentials endpoint (currently 405), or +3. An operator-endorsed or T2 credential path.