From a change
to a coherent record.

1. Open a workspace

Explore the fictional demo without an account, or register with a name, email, password, and agreement to the Terms. A registered workspace starts empty and saves on the server. Email ownership is not yet verified at signup.

Demo edits stay in local storage in this browser. Use fictional information on shared devices. Privacy choices can clear local demo data.

2. Define a release

Choose New release. Add the title, scope, category, and target date. Add an optional owner label and document the rollout and rollback plans. Start in Draft or In review. Up to 200 releases can be stored per individual account.

Owner labels are descriptive: they do not invite a colleague, send a notification, or establish approval.

3. Build the checklist

Choose New check and link it to a release. Enter the title and evidence or next step. Choose Quality, Operations, or Security. An owner label and evidence URL are optional.

URLs must use HTTP or HTTPS without embedded credentials. The software stores your reference without fetching, executing, or verifying it. Mark passed only after your own review. Up to 2,000 checks per account.

4. Review readiness

Ready requires rollout and rollback plans of at least 30 characters each, at least one linked check, and all linked checks passed. A progress bar counts passed checks; it does not represent independently measured safety.

Adding, editing, moving, or removing a check reopens affected Ready releases as In review. A move can reopen both old and new releases. Revisit the current record before marking Ready again.

Ready does not execute deployment, approve production access, or certify compliance. This pilot has no CI/CD connection or automated testing.

5. Export and remove

Brief TXT downloads the release scope, both plans, and linked checks as plain text. Releases CSV, Checks CSV, and Workspace JSON include all records even when search or filters hide some. JSON includes the most recent 100 activity events.

CSV formula-leading entries are escaped. Review exports before opening or sharing. They contain your entered content, not copies of external linked documents.

Deleting a release also deletes its checks. Activity can retain short titles after a record is deleted. Account deletion removes the active account and related releases, checks, activity, and reset tokens. Export first if needed.

6. Account and support

Passwords must be 12–72 bytes. Some characters use multiple bytes. Reset links expire after 30 minutes and work once. A successful password reset invalidates old authenticated sessions.

Do not store secrets, production credentials, sensitive regulated information, or unauthorized materials. Contact raja@arcweaversystems.net for help or business requirements. No support response-time commitment is made for the pilot.