API + BT workflow demos

.markdownlint-cli2.yaml

@@ -27,10 +27,11 @@ config:
   # Disabled because conversion from TeX to markdown produces invalid links
   # We might eventually be able to re-enable this one.
   "MD051": false
+  # 060 - Table column style
+  "MD060": false
 ignores:
   - "plan/**"
-  - "prompts/**"
   - "specs/**"
   - "wip_notes/**"
   - "AGENTS.md"
-  - "node_modules/**"
+  - "node_modules/**"

docker/Dockerfile

@@ -43,3 +43,47 @@ FROM dependencies AS receive-report-demo
 ENV PYTHONPATH=/app
 # The BASE_URL in the script will be overridden via environment variable
 CMD ["uv", "run", "python", "-m", "vultron.scripts.receive_report_demo"]
+
+FROM dependencies AS initialize-case-demo
+ENV PYTHONPATH=/app
+CMD ["uv", "run", "python", "-m", "vultron.scripts.initialize_case_demo"]
+
+FROM dependencies AS establish-embargo-demo
+ENV PYTHONPATH=/app
+CMD ["uv", "run", "python", "-m", "vultron.scripts.establish_embargo_demo"]
+
+FROM dependencies AS invite-actor-demo
+ENV PYTHONPATH=/app
+CMD ["uv", "run", "python", "-m", "vultron.scripts.invite_actor_demo"]
+
+FROM dependencies AS status-updates-demo
+ENV PYTHONPATH=/app
+CMD ["uv", "run", "python", "-m", "vultron.scripts.status_updates_demo"]
+
+FROM dependencies AS suggest-actor-demo
+ENV PYTHONPATH=/app
+CMD ["uv", "run", "python", "-m", "vultron.scripts.suggest_actor_demo"]
+
+FROM dependencies AS transfer-ownership-demo
+ENV PYTHONPATH=/app
+CMD ["uv", "run", "python", "-m", "vultron.scripts.transfer_ownership_demo"]
+
+FROM dependencies AS acknowledge-demo
+ENV PYTHONPATH=/app
+CMD ["uv", "run", "python", "-m", "vultron.scripts.acknowledge_demo"]
+
+FROM dependencies AS manage-case-demo
+ENV PYTHONPATH=/app
+CMD ["uv", "run", "python", "-m", "vultron.scripts.manage_case_demo"]
+
+FROM dependencies AS initialize-participant-demo
+ENV PYTHONPATH=/app
+CMD ["uv", "run", "python", "-m", "vultron.scripts.initialize_participant_demo"]
+
+FROM dependencies AS manage-embargo-demo
+ENV PYTHONPATH=/app
+CMD ["uv", "run", "python", "-m", "vultron.scripts.manage_embargo_demo"]
+
+FROM dependencies AS manage-participants-demo
+ENV PYTHONPATH=/app
+CMD ["uv", "run", "python", "-m", "vultron.scripts.manage_participants_demo"]

docker/README.md

@@ -6,23 +6,30 @@ This docker-compose setup provides several containerized services:
 
 - **api-dev**: Development API server running on port 7999
 - **receive-report-demo**: Demo script that sends vulnerability reports to the API server
+- **initialize-case-demo**: Demo script that shows the case initialization workflow
+- **establish-embargo-demo**: Demo script that demonstrates the embargo establishment workflow
+- **invite-actor-demo**: Demo script that demonstrates inviting an actor to a case
+- **status-updates-demo**: Demo script that demonstrates case and participant status updates
+- **suggest-actor-demo**: Demo script that demonstrates recommending actors for a case
+- **transfer-ownership-demo**: Demo script that demonstrates transferring case ownership
 - **test**: Run pytest test suite
 - **docs**: Documentation server on port 8000
 - **vultrabot-demo**: Vultrabot demonstration
 
 ## Running the API Server and Demo
 
-To run both the API server and the receive report demo together:
+To run both the API server and a demo together, for example:
 
 ```bash
 docker-compose up api-dev receive-report-demo
 ```
 
-The demo container will:
+Replace `receive-report-demo` with any of the demo service names listed above.
+Each demo container will:
 
 1. Wait for the API server to start
 2. Connect to the API via the internal Docker network
-3. Execute the three demonstration workflows
+3. Execute the demonstration workflow
 4. Display results and exit
 
 The API server remains running and accessible on `http://localhost:7999`.

docker/docker-compose.yml

@@ -93,6 +93,204 @@ services:
     networks:
       - vultron-network
 
+  initialize-case-demo:
+    build:
+      context: ..
+      dockerfile: docker/Dockerfile
+      target: initialize-case-demo
+    image: ${PROJECT_NAME}-initialize-case-demo:latest
+    depends_on:
+      api-dev:
+        condition: service_healthy
+    volumes:
+      - "../vultron:/app/vultron"
+      - "/app/.venv"
+    environment:
+      - PYTHONPATH=/app
+      - VULTRON_API_BASE_URL=http://api-dev:7999/api/v2
+    networks:
+      - vultron-network
+
+  establish-embargo-demo:
+    build:
+      context: ..
+      dockerfile: docker/Dockerfile
+      target: establish-embargo-demo
+    image: ${PROJECT_NAME}-establish-embargo-demo:latest
+    depends_on:
+      api-dev:
+        condition: service_healthy
+    volumes:
+      - "../vultron:/app/vultron"
+      - "/app/.venv"
+    environment:
+      - PYTHONPATH=/app
+      - VULTRON_API_BASE_URL=http://api-dev:7999/api/v2
+    networks:
+      - vultron-network
+
+  invite-actor-demo:
+    build:
+      context: ..
+      dockerfile: docker/Dockerfile
+      target: invite-actor-demo
+    image: ${PROJECT_NAME}-invite-actor-demo:latest
+    depends_on:
+      api-dev:
+        condition: service_healthy
+    volumes:
+      - "../vultron:/app/vultron"
+      - "/app/.venv"
+    environment:
+      - PYTHONPATH=/app
+      - VULTRON_API_BASE_URL=http://api-dev:7999/api/v2
+    networks:
+      - vultron-network
+
+  status-updates-demo:
+    build:
+      context: ..
+      dockerfile: docker/Dockerfile
+      target: status-updates-demo
+    image: ${PROJECT_NAME}-status-updates-demo:latest
+    depends_on:
+      api-dev:
+        condition: service_healthy
+    volumes:
+      - "../vultron:/app/vultron"
+      - "/app/.venv"
+    environment:
+      - PYTHONPATH=/app
+      - VULTRON_API_BASE_URL=http://api-dev:7999/api/v2
+    networks:
+      - vultron-network
+
+  suggest-actor-demo:
+    build:
+      context: ..
+      dockerfile: docker/Dockerfile
+      target: suggest-actor-demo
+    image: ${PROJECT_NAME}-suggest-actor-demo:latest
+    depends_on:
+      api-dev:
+        condition: service_healthy
+    volumes:
+      - "../vultron:/app/vultron"
+      - "/app/.venv"
+    environment:
+      - PYTHONPATH=/app
+      - VULTRON_API_BASE_URL=http://api-dev:7999/api/v2
+    networks:
+      - vultron-network
+
+  transfer-ownership-demo:
+    build:
+      context: ..
+      dockerfile: docker/Dockerfile
+      target: transfer-ownership-demo
+    image: ${PROJECT_NAME}-transfer-ownership-demo:latest
+    depends_on:
+      api-dev:
+        condition: service_healthy
+    volumes:
+      - "../vultron:/app/vultron"
+      - "/app/.venv"
+    environment:
+      - PYTHONPATH=/app
+      - VULTRON_API_BASE_URL=http://api-dev:7999/api/v2
+    networks:
+      - vultron-network
+
+  acknowledge-demo:
+    build:
+      context: ..
+      dockerfile: docker/Dockerfile
+      target: acknowledge-demo
+    image: ${PROJECT_NAME}-acknowledge-demo:latest
+    depends_on:
+      api-dev:
+        condition: service_healthy
+    volumes:
+      - "../vultron:/app/vultron"
+      - "/app/.venv"
+    environment:
+      - PYTHONPATH=/app
+      - VULTRON_API_BASE_URL=http://api-dev:7999/api/v2
+    networks:
+      - vultron-network
+
+  manage-case-demo:
+    build:
+      context: ..
+      dockerfile: docker/Dockerfile
+      target: manage-case-demo
+    image: ${PROJECT_NAME}-manage-case-demo:latest
+    depends_on:
+      api-dev:
+        condition: service_healthy
+    volumes:
+      - "../vultron:/app/vultron"
+      - "/app/.venv"
+    environment:
+      - PYTHONPATH=/app
+      - VULTRON_API_BASE_URL=http://api-dev:7999/api/v2
+    networks:
+      - vultron-network
+
+  initialize-participant-demo:
+    build:
+      context: ..
+      dockerfile: docker/Dockerfile
+      target: initialize-participant-demo
+    image: ${PROJECT_NAME}-initialize-participant-demo:latest
+    depends_on:
+      api-dev:
+        condition: service_healthy
+    volumes:
+      - "../vultron:/app/vultron"
+      - "/app/.venv"
+    environment:
+      - PYTHONPATH=/app
+      - VULTRON_API_BASE_URL=http://api-dev:7999/api/v2
+    networks:
+      - vultron-network
+
+  manage-embargo-demo:
+    build:
+      context: ..
+      dockerfile: docker/Dockerfile
+      target: manage-embargo-demo
+    image: ${PROJECT_NAME}-manage-embargo-demo:latest
+    depends_on:
+      api-dev:
+        condition: service_healthy
+    volumes:
+      - "../vultron:/app/vultron"
+      - "/app/.venv"
+    environment:
+      - PYTHONPATH=/app
+      - VULTRON_API_BASE_URL=http://api-dev:7999/api/v2
+    networks:
+      - vultron-network
+
+  manage-participants-demo:
+    build:
+      context: ..
+      dockerfile: docker/Dockerfile
+      target: manage-participants-demo
+    image: ${PROJECT_NAME}-manage-participants-demo:latest
+    depends_on:
+      api-dev:
+        condition: service_healthy
+    volumes:
+      - "../vultron:/app/vultron"
+      - "/app/.venv"
+    environment:
+      - PYTHONPATH=/app
+      - VULTRON_API_BASE_URL=http://api-dev:7999/api/v2
+    networks:
+      - vultron-network
+
 networks:
   vultron-network:
     driver: bridge

docs/howto/activitypub/activities/invite_actor.md

@@ -20,10 +20,10 @@ sequenceDiagram
     actor A as Actor
     participant C as Case
     activate O
-    O ->>+ A: Invite(object=Case)
+    O ->>+ A: Invite(actor=CaseOwner, object=Actor, target=Case)
     note over A: Consider invitation
     alt Accept Invitation
-        A -->> O: Accept(object=Case, inReplyTo=Invite)
+        A -->> O: Accept(object=Invite)
         alt Create CaseParticipant
         O ->> C: Create(object=CaseParticipant(actor=Actor), target=Case)
         else Add CaseParticipant
@@ -32,7 +32,7 @@ sequenceDiagram
         end
         note over C: Actor becomes participant in case
     else Reject Invitation
-        A -->> O: Reject(object=Case, inReplyTo=Invite)
+        A -->> O: Reject(object=Invite)
         note over C: Actor is not participant in case
     end
     deactivate A

docs/howto/activitypub/activities/manage_case.md

@@ -75,15 +75,13 @@ flowchart TB
 
 !!! tip "Re-Engaging a Case"
 
-    The `RmReEngageCase` activity is used to re-engage a case that has been
-    deferred. Deferring a case is modeled as an `as:Ignore`
-    activity, since it is indicating that a participant has not entirely left
-    the case, but has instead deferred their participation for a period of
-    time. Re-engaging a case is modeled as an `as:Undo` activity, since it is
-    undoing the `as:Ignore` activity that was used to defer the case.
-    Alternatively, we could have just used the same `RmEngageCase` (`as:Join`) 
-    activity. That might still be a better option, but we'll leave it as an
-    implementation choice for now.
+    Re-engaging a deferred case uses the same `RmEngageCase` (`as:Join`)
+    activity. Because the RM model permits reversible transitions between
+    `ACCEPTED` and `DEFERRED`, re-engagement is simply an `accept` transition
+    emitted from the `DEFERRED` state — there is no separate `RmReEngageCase`
+    activity. Using `as:Undo` was considered but rejected: `Undo` implies
+    retracting the *effects* of a prior action, whereas re-engagement is a
+    forward state transition.
 
 {% include-markdown "./_close_case.md" heading-offset=1 %}
 {% include-markdown "./_close_report.md" heading-offset=1 %}

docs/howto/activitypub/activities/suggest_actor.md

@@ -56,10 +56,10 @@ sequenceDiagram
     activate A
     C -->+ B: Observe suggestion
     alt Accept Suggestion
-        B -->> C: Accept(object=Actor, target=Case, inReplyTo=Offer)
-        B ->>+ D: Invite(object=Case, target=Actor)
+        B -->> C: Accept(object=Offer)
+        B ->>+ D: Invite(actor=CaseOwner, object=Actor, target=Case)
     else Reject Suggestion
-        B -->> C: Reject(object=Actor, target=Case, inReplyTo=Offer)
+        B -->> C: Reject(object=Offer)
     end
     deactivate B
     C --> A: Observe response

docs/howto/activitypub/activities/transfer_ownership.md

@@ -28,11 +28,11 @@ sequenceDiagram
     note over B: Consider offer
     activate B
     alt Accept Offer
-        B -->> A: Accept(object=Case, inReplyTo=Offer)
+        B -->> A: Accept(object=Offer)
         A ->> C: Update(object=Case)
         note over C: Case has new owner
     else Reject Offer
-        B -->> A: Reject(object=Case, inReplyTo=Offer)
+        B -->> A: Reject(object=Offer)
         note over C: Case ownership unchanged
     end
     deactivate B