hacklab/T-HUB
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1

docs: publish governance, governed boosts, receipts, OIDC phase 2, files SSO

Browse source 
Engineering guide: session/refresh/logout architecture, publish-governance
and amplify gating sections, file map to migrations 001-034. Admin guide:
governance administration, files-SSO operations, verification harnesses,
migration list + deploy order + 034 session note. User manual: calendar
receipt badges, boost gating, connections governance note (replaces the
stale 'stub' statuses). Design doc 2026-10-13: marked implemented with the
as-shipped phase 2. Wiki (EN/ES): Drive sign-in + boosts/approvals.
README: governance + Files SSO bullets.
This commit is contained in:
glass beadian 2026-10-14 11:52:48 +00:00
parent 643fbb94bc
commit b8671113f5
7 changed files with 113 additions and 21 deletions
Download patch file Download diff file Expand all files Collapse all files

13
docs/user-manual-v2.md
View file

@ -152,6 +152,7 @@
- **Live.** Reads `GET /connections` for the workspace. A new workspace shows *"No channels connected yet"*, followed by one dashed *not connected* card per known platform.
- **Connect buttons.** **Connect account**, **Connect**, **Reconnect** and **Remove** are **disabled when live**. Their tooltip reads: *"OAuth connect flows arrive with the connector wiring phase"*. **There is no way to add a channel from the UI today.**
- **Publish governance** (per connection): admins choose who signs off each publish — manual, automatic on approval, or an admin vote (1 / majority / consensus). Managed via the API (`PATCH /connections/:id/publish-governance`, admin guide §6.1); there is no web control for it yet. A governed connection holds publishes and boosts with *"awaiting publish approval"* until the admins' poll passes.
- **Each connected card** (seen in sample mode) shows:
- a health badge (*healthy*, *token expiring*, *needs credentials*)
- capability chips (`publishText`, `amplifyRepost`, `feed`, `directMessages`, `comments`…)
@ -257,17 +258,11 @@ Invite emails and invite acceptance are **not wired**. The page says so itself.
## 11. Calendar, Approvals, Analytics, Settings
**Status: stub.** Each of these four screens is a placeholder reading *"Arrives with WP3 (publishing pipeline)."*
**Calendar** is the scheduled-drafts list (live against the API when signed in). Each row shows its draft, its schedule, and — since the receipts feature — a **dispatch receipt badge** for any draft that has been dispatched: the latest attempt's outcome (`completed` green, `failed` red, `in progress`/`ready` amber), with an **open ↗** link when the platform returned a post URL. Badges refresh on load, on schedule changes, every 30 s, and on **Refresh**. Drafts never dispatched show no badge.
| Calendar | Approvals |
|---|---|
| ![](manual/screenshots/desktop-calendar.png) | ![](manual/screenshots/desktop-approvals.png) |
**Boosts (amplify).** A boost reposts or quotes someone else's post through one of your connections, and it is governed like any publish: the draft must be approved, and if the connection's publish governance is an admin mode (see the admin guide §6.1), the boost is held with *"awaiting publish approval"* until admins approve the publish poll — then re-send it and it executes. On ungoverned connections a boost executes immediately.
| Analytics | Settings |
|---|---|
| ![](manual/screenshots/desktop-analytics.png) | ![](manual/screenshots/desktop-settings.png) |
The approval *state machine* does exist in the API: drafts move editing → in_review → approved, verified in §5. There is just no review-queue screen yet.
**Approvals / Analytics / Settings**: Approvals renders the review queue; Analytics and Settings are live screens (workspace settings, sessions, connections).
---