glas-harness/workplans/GLAS-WP-0016-fi-research-brief-profile.md

id	type	title	domain	repo	status	flavor	owner	topic_slug	created	updated	state_hub_workstream_id
GLAS-WP-0016	workplan	Versioned Glas profile for the FI daily research brief	infotech	glas-harness	ready	implementation	claude	fi-research-brief-profile	2026-10-13	2026-10-13	1254b220-fd97-5c84-a0e0-ef2de10972c4

FI daily research brief profile

Request: freedom-intelligence message c7f2df46 (FI-WP-0005-T05, 2026-09-22) asks for harness.fi-research-brief@1.0.0. FI's profile-absent routing expires 2026-12-31; FI-WP-0005-T07 wires the canary only after a positive sandboxed proof run. Owner declaration: freedom-intelligence/activity-definitions/fi-daily-research-brief.declaration.yaml. Egress list: freedom-intelligence/docs/sources-egress.yaml (17 hosts, :443). Publication design: docs/publish-grant-design.md.

Add the Glas profile harness.fi-research-brief@1.0.0

id: GLAS-WP-0016-T01
status: todo
priority: high
state_hub_task_id: "e49776ae-a28a-527f-aece-1f08a05c044a"

Add profiles/harness.fi-research-brief.yaml: rein-aharness, session_style unattended, model_class frontier, model pinned by Glas (same pin as harness.agent-dev-local 1.1.1 unless the operator chooses otherwise), limits timeout 1800s / max_turns 60, max_budget_usd inside an accepted spend envelope, sandbox profile from T02, tool profile from T03, documented rollback pin. operational_readiness.status: unverified until T04 passes. Catalog validation (glas-harness profiles) and tests must pass. Depends on T02/T03 names being agreed, not on their release.

Add the sand-boxer egress sandbox profile

id: GLAS-WP-0016-T02
status: todo
priority: high
state_hub_task_id: "d79ad740-eec6-5e93-9d90-49475982a900"

Owner: sand-boxer. Request a bwrap profile (working name profile.bwrap-fi-research) with network.default: deny and network.egress equal to the model route plus exactly the 17 hosts in FI's sources-egress.yaml, per sand-boxer/docs/bwrap-egress.md (exact lowercase DNS names, :443, no wildcards or IP literals). Owner config allowed_egress must be a superset. Glas sends the handoff and records the owner's return.

Add the rein-aharness research tool profile

id: GLAS-WP-0016-T03
status: todo
priority: high
state_hub_task_id: "cd49e97f-13f4-5563-a7cf-68f7a138bd85"

Owner: rein-aharness. Request a tool profile (working name green-research-commit): read/edit tools, HTTPS fetch through the sandbox proxy, git add/commit/status/log/diff limited to granted paths (briefs/**), no push and no arbitrary shell. Publication is not part of the tool profile; it is the deterministic publisher step in docs/publish-grant-design.md.

Prove one sandboxed run and mark the profile ready

id: GLAS-WP-0016-T04
status: wait
priority: high
blocking_reason: "Depends on T01-T03 and on the publisher owner (T05)."
state_hub_task_id: "6faf1b1c-164d-5d6d-8dad-6cf920a5fd6c"

Run one bounded brief through the profile inside the sandbox: egress limited to the declared hosts, exactly one new file under briefs/, one commit, no push from the session. Publish evidence under docs/evidence/, then set operational_readiness.status: ready and notify FI for FI-WP-0005-T07.

Operator decision: owner of the publish-grant publisher

id: GLAS-WP-0016-T05
status: wait
needs_human: true
priority: high
blocking_reason: "Operator decision: which subsystem owns the deterministic publisher (recommendation: Activity Core)."
state_hub_task_id: "e91fa370-236e-56c8-b88d-3272aec40dc1"

docs/publish-grant-design.md defines one path-scoped publish grant for FI and assembly-checkpoint. Open: who owns the publisher step and its push credentials. Recommendation: Activity Core. Resolve before T04 publishes.

Operator decision: is a sandboxed pinned agent a host installation?

id: GLAS-WP-0016-T06
status: wait
needs_human: true
priority: high
blocking_reason: "Operator decision on FI's playbook question; FI decides its rhythm on that basis."
state_hub_task_id: "d1584459-dd09-5f60-b298-0c56c2a300b0"

FI's playbook forbids installing Claude Code / Codex on railiance01 for this rhythm. Question: does a pinned agent executable that runs only inside the Glas bwrap sandbox count as a host installation? Glas view: no. The binary is a pinned runtime artifact owned by rein-aharness/sand-boxer, not on the host PATH, not user-installed, carries no host credentials and runs only under deny-default egress. Answer FI explicitly once the operator decides.