Weiming Intelligence

Personal AI.

Let AI hold onto one continuous line of work. LinX keeps tasks moving, and xpod holds secrets, permissions, and services inside your boundary.

  • Context
  • Boundary
  • Execution
  • Stays yours
Chats
S
Secretary 09:48
All 142/142 passed, DEV healthy.
🔑
Secrets inbox 09:18
1 pending
IT
Integration Yesterday
Done
Secretary
Me
Are the tests done?
S
Secretary
All 142/142 passed. DEV health check passed, integration queued, ETA 12 min.
Me
Good, keep pushing the rest.
S
Secretary
Got it. I'll pause when secrets or permissions are needed.
Type a message…

01

Your AI Secretary Never Stops

Standard AI is a passive chatbot. A Secretary is an active driver. It pushes work forward and waits for state changes without needing you to click "continue".

Chats
RT 3
release-train 09:48
Secretary: Deploy needs token scope…
IT
Integration 09:28
Queued
🔑
Secrets inbox 09:18
1 pending
release-train Delegated · Secretary driving
Me
Run the tests, push to DEV if they pass, call me if anything breaks.
S
Secretary
Got it. I'll take over this workline.
Secretary decides · 5s
S
Secretary → build-worker instruction
Run unit tests and report back.
BW
build-worker
142/142 passed in 47s.
S
Secretary
Tests passed. Checking DEV.
Secretary decides · 3s
S
Secretary
Deploy needs render_api_token scope. Exceeds my authority. Waiting for you.
Waiting for user · ∞
Secretary is driving this workline…
Chats
⚠️ 1
Import anomaly 14:22
Secretary: Found 23 duplicates…
RT
release-train 09:48
On track
Import anomaly Secretary initiated
Secretary initiated this conversation
S
Secretary anomaly
Import anomaly detected: 23 duplicate WeChat records from two exports of the same group. I've paused this batch. No existing data affected.
S
Secretary
How would you like to handle it?
Deduplicate Discard Show raw
Reply to Secretary…
Inbox
📋
Approvals
3 pending · 12 done
📐
Rules
3 rules
Approval Queue 3 pending
render_api_token scope Secretary → build-worker · 09:48
pending
Prod DB read-only Secretary → data-worker · 09:32
pending
DEV deploy Secretary → build-worker · 09:42
Secretary · 5s
Unit tests Secretary → build-worker · 09:39
auto

Rules

Non-prod tests Auto-approve
Secrets & prod Require human
DEV deploy Secretary (5s)

02

All Your Pieces, In One Place

Conversation, files, and running services come back into one workspace. The AI finally sees the full thread of work instead of isolated prompts.

Files
📥
Data Import
6 sources · 3 syncing
📄
Local Files
1,204 files
Data Import Live · 6 sources
💬WeChat
2,847 msgs
syncing
🔖Bookmarks
186
syncing
📁Files
1,204
scanning
✉️Email
523
done
📅Calendar
89
done
📝Notes
queued
14:23:08WeChat · wrote 34 messages
14:23:05Bookmarks · 3 linked
14:23:01Files · 12 to index
4,849 records written to Pod pod.ganlu.me
Contacts
Zhang Ming
7 semantic links
Li Wei
3 links
RT
release-train
Project · 12 links
Zhang Ming 7 semantic links
💬 WECHAT
48 messages
Recent: deployment plan
✉️ EMAIL
12 threads
Recent: Q2 budget
📅 CALENDAR
Next Tue 14:00
Technical review
📁 FILES
3 shared docs
deploy-plan.md, budget-q2.xlsx
These links come from semantic relationships in your data, not from any single app. Switch clients, and the links remain.
Settings
🔒
Pod
pod.ganlu.me
🔑
App Access
3 apps
Pod local
URLhttps://pod.ganlu.me/
WebIDid.ganlu.me/profile/card#me
StorageLocal · ~/solid-pod/
Used2.4 GB

App Access

LinX
All data
read-write
Notes App
Notes container
read-only
Analytics
Calendar + Email
revoked
Your data lives in your own Pod. Apps need permission, and you can revoke anytime.

03

One Secretary, Many Agents

You interact with one aligned Secretary that orchestrates other agents. Mechanical tasks run automatically; sensitive actions pause for your approval.

Chats
S
Secretary 10:15
Got it. Setting up this role.
RT
release-train 09:48
On track
Secretary Team management
Me
I need a code review Agent. Read-only on repo, no production access.
S
Secretary
Got it. Setting up this role.
CR
code-reviewer Code Review Specialist
Code reporead-only
PR commentsread-write
Productiondenied
Secretsdenied

Team

secretarySecretaryaligned
build-workerBuildrunning
doc-workerDocsidle
code-reviewerReviewnew
Chats
🏢 5
release-train group 11:05
doc-worker: changelog synced…
S
Secretary 10:15
Team management
release-train group
Secretary +3
S
Secretary
Team, release-train final stage. Assignments:
S
Secretary assignments
→ build-worker: integration tests then SIT
→ code-reviewer: review last 3 PRs
→ doc-worker: sync changelog
BW
build-worker
Integration started, ETA 8 min.
CR
code-reviewer risk
PR #142 has SQL injection risk. Block merge.
S
Secretary decision
Noted. PR #142 paused. build-worker, skip and continue.
DW
doc-worker
Changelog synced. Waiting for version number.
Secretary coordinating…
Chats
🔑 1
Key Request 11:14
Secretary: Key provisioned…
RT
release-train 11:12
Waiting for key
Key Request render_api_token
BW
build-worker
Need render_api_token for SIT deploy, but I don't have access.
S
Secretary
I'll handle it. Requesting scoped token from xpod.

xpod Key Request

render_api_token
RequesterSecretary → build-worker
PurposeSIT deploy
Scopewrite-only · SIT · 1h
Statuswaiting for approval
Me
Approved.
S
Secretary
Key provisioned, distributed to build-worker.
BW
build-worker
Received scoped token. Deploying.
Type a message…

Start with LinX

When you need runtime and boundary next, move into xpod and docs.