# Portability Notes
This package is extracted from the `herdr-trial` workspace. Historical ADR text may mention the original `outputs/...` paths because those paths are part of the target-workspace convention established during the design session.
## Package Paths
Inside this clean package:
- ADRs live in `decisions/`.
- Skills live in `skills/`.
- Config and helper-tool prototypes live in `tools/`.
- Example status, summary, dashboard, and audit artifacts live in `examples/`.
## Target Project Paths
When applying the protocol inside another project, the recommended runtime artifact paths remain:
- `outputs/decisions/` for project-local ADRs or copied protocol decisions.
- `outputs/skills/` for project-local skills.
- `outputs/tools/` for profile config and helper tools.
- `outputs/sessions/<session_id>/status.md` for rolling status.
- `outputs/sessions/<session_id>/summary.md` for end-of-session summary.
- `outputs/sessions/<session_id>/audit.md` for audit records.
- `outputs/dashboard.md` for aggregate operator dashboard.
Delivery proof boundary:
- Protocol-shaped text printed by a sender is `drafted`, not `sent`.
- `sent` requires a real transport send, helper-tool confirmation, or explicit operator relay.
- `observed` requires receiver/operator confirmation that the target saw the message.
- Portable audit records should preserve this distinction even when the transport has no durable delivery log.
## Herdr-Specific Pieces
Herdr-specific profile values currently include:
- `transport.default: herdr`
- `transport.address_source: pane_list.pane_id`
- `transport.workspace_id_source: pane_list.workspace_id`
- `local_address_alias.env_var: HERDR_PANE_ID`
Other transports should provide their own address source and workspace/thread identifiers while keeping the ADR 001-004 message and identity model.