Runs live, versioned Python application objects on one VM, with a suite of apps: projects, notes, tasks, files and more.

0 downloads

Download zip
Clone
Clone with git
git clone https://gitstable.com/git/askrobots/dbbasic-object-server.git
HTTPS
https://gitstable.com/git/askrobots/dbbasic-object-server.git
SSH
ssh://git@gitstable.com:2222/askrobots/dbbasic-object-server.git

Cloning needs no sign-in. Pushing over HTTPS asks for your username and an access token. SSH needs your key under SSH keys.

danq9 signup: the person chooses the password and name on the confirm page 83c7aa6 2 weeks, 5 days ago History
rules.json · 2.1 KB · 32 lines
1{
2 "rules": [
3 {
4 "effect": "allow",
5 "principal": "registered",
6 "actions": ["execute"],
7 "object_id": "action_agent_heartbeat",
8 "reason": "any registered principal may say it is still here, and only about ITSELF -- the object takes agent_id from _identity and never from the body, so a heartbeat cannot be forged on another agent's behalf. That matters more than it looks: a heartbeat is the evidence something is alive, and evidence one party can manufacture about another is not evidence. Registered rather than admin because an agent provisioned with its own API key must be able to introduce itself without an operator present"
9 },
10 {
11 "effect": "allow",
12 "principal": "registered",
13 "actions": ["execute"],
14 "object_id": "site_agents",
15 "reason": "operator-facing rather than public: the board names every agent, its purpose, its capabilities and its spend against cap, which together describe how a business runs its automation. Registered rather than admin because 'is everything still working' is a question anyone on shift gets asked, and a status board only the owner can open is a status board nobody reads"
16 },
17 {
18 "effect": "allow",
19 "principal": "registered",
20 "actions": ["read"],
21 "collection": "agent_registry",
22 "reason": "read for everyone registered, so the board and the generative table agree. No CREATE: action_agent_heartbeat is the one door in, because a registration typed by hand is an agent that never introduced itself and may not exist. No DELETE either -- a retired agent's row is what keeps months of change-log actors legible, and status=retired is how one goes away"
23 },
24 {
25 "effect": "allow",
26 "principal": "role:admin",
27 "actions": ["update"],
28 "collection": "agent_registry",
29 "reason": "an OPERATOR may pause, suspend or retire an agent, and set its spend cap -- the controls that exist for the case where an agent is misbehaving and the person who has to stop it is not the agent. Deliberately admin-only: an agent that could raise its own spend cap has no spend cap"
30 }
31 ]
32}