# Purple Envelope

Status: Draft

## Purpose

Unknown.

Initial note: Loc needs to run the Purple Envelope jobs, and the process has unresolved weirdness that needs diagnosis.

## Owner

- Primary owner: Unknown
- Backup owner: Unknown
- Escalation contact: Unknown
- Team member involved: Loc

## Summary

Unknown.

## Trigger

- Scheduled task: Unknown
- SQL Agent job: Unknown
- Service: Unknown
- Script: Unknown
- Manual action: Unknown
- Application-triggered: Unknown
- Other: Unknown

## Schedule

- Frequency: Unknown
- Expected start time: Unknown
- Expected duration: Unknown
- Time zone: Unknown
- Blackout windows: Unknown

## Runtime Location

- Server/workstation: Unknown
- Application: Unknown
- Script path: Unknown
- Working directory: Unknown
- Account/context: Unknown

Do not document passwords or secrets.

## Inputs

| Input | Location | Format | Required | Notes |
| --- | --- | --- | --- | --- |
| Unknown | Unknown | Unknown | Unknown | Need to identify files or batches processed by Purple Envelope. |

## Outputs

| Output | Location | Format | Recipient/System | Notes |
| --- | --- | --- | --- | --- |
| Unknown | Unknown | Unknown | Unknown | Need to identify expected output. |

## Dependencies

- File shares: Unknown
- Databases: Unknown
- External systems: Unknown
- PDF tooling: Unknown
- Permissions: Unknown
- Network access: Unknown
- Team member access/setup: Loc

## Processing Steps

Draft expected flow:

```text
receive or identify Purple Envelope input
   ↓
run expected job/process
   ↓
produce output
   ↓
verify output
   ↓
archive or hand off result
```

## Success Criteria

- Loc can start the expected Purple Envelope job.
- The job runs without unexpected errors.
- Expected output is created.
- Output is validated.
- Any downstream handoff completes.
- The weird behavior is either resolved or documented with a known workaround.

## Failure Modes

| Failure | Symptom | Likely Cause | First Check | Escalation |
| --- | --- | --- | --- | --- |
| Loc cannot run job | Job does not start or fails immediately | Access, setup, permissions, path, missing dependency | Compare Loc setup to known-good setup | Unknown |
| Weird process behavior | Unexpected output or inconsistent run | Unknown | Capture exact step, input, output, and logs | Unknown |
| Output missing | Job completes but files are absent | Wrong destination, permission, failed processing | Check logs and output path | Unknown |

## Troubleshooting

1. Ask Loc to capture the exact failure point.
2. Record the input/batch used.
3. Record the command, UI step, or job trigger Loc used.
4. Compare Loc's environment/access to a known-good environment.
5. Check logs for the same time window.
6. Confirm expected output path and file naming.
7. Decide whether this is a setup issue, data issue, process issue, or code issue.

## Reprocessing Rules

- Can this job be rerun safely? Unknown.
- What must be cleaned up before rerun? Unknown.
- What duplicate risks exist? Unknown.
- Who approves reprocessing? Unknown.

## Retention / Cleanup

- Input retention: Unknown
- Output retention: Unknown
- Archive location: Unknown
- Cleanup schedule: Unknown
- Backup requirements: Unknown

## Security Notes

- Sensitive data handled: Unknown
- Access restrictions: Unknown
- Secrets/configuration location: Unknown
- Logging restrictions: Do not log credentials or sensitive content.

## Open Questions

- What does Purple Envelope process?
- What command, application, or scheduled job runs it?
- What does Loc need in order to run it?
- What is the exact weirdness?
- Is there a known-good machine/user/process for comparison?
- What output proves the job succeeded?
- Can the job be rerun safely after a failed attempt?

## Change History

| Date | Change | Author |
| --- | --- | --- |
| 2026-09-01 | Initial draft scaffold | Codex |