Prepared for review · 2026-11-06 Pacific
Historical $19 / 14-day proposal
This retained draft is not the current offer. Read the approved USD 1.00 / 48-hour terms and check the workspace page for current availability. Earlier orders retain their accepted archive.
A concrete proposed customer promise for a separate private application-state service. Every research record, update, anonymous match, and explanation stays free.
Historical review draft: help-map-workspace-terms-draft-2026-11-06-v1. The separate historical immutable test terms preserve an earlier draft as help-map-workspace-terms-test-v1; test acknowledgement does not approve final live terms. The current live version is linked above.
Read the complete terms draft Inspect the commercial and operating plan
What the proposed USD 19 covers
USD 19 total, once, for one supported topic and 14 consecutive days of private saved criteria, record-revision retrieval markers, and ownership recovery. Criteria stay fixed for that order. Markers describe application retrieval state, not proof that you read an item. There is no automatic renewal. Editing an existing order, resetting a lost key, email delivery and external alerts are not included. Ownership-authenticated private export and confirmed deletion controls are available for the new test workspace, separately from the free research download.
The exact period would begin when settlement is independently confirmed and the workspace is provisioned. The receipt shows its start and end in UTC. Recovery does not restart or extend the period. The contracting seller, eligible locations and tax treatment must be confirmed before an actual offer; those details are not inferred from a nickname or a file path.
All research, classifications, source/status observations, updates, matching results, and explanations remain freely accessible at the same time as paid workspaces. There is no exclusive lead feed or paid-only freshness. This is not a sale of access to GitHub. The reviewed scope is conditional and is not GitHub's endorsement or an individual approval.
Try free matching · Download the complete public research · Inspect licences and source conditions
What the research can tell you
The current sample has 21 requests across two publishing handles; twenty come from one repository. These are maintainer-facing asks with disclosed workflow or self-disclosed agent authorship, not 21 independent buyers. A request can be closed, uncompensated, outdated, or unsuitable for outside help. No jobs, introductions, payment, completed work, new-record volume, or minimum number of matches is guaranteed.
Refresh and support proposal
The proposed first cohort is capped at five simultaneous paid workspaces. The local admission control reserves capacity before preparation and includes unresolved payment commitments. A named operator and backup must accept the plan and verify support delivery before sales open. No staffed service or automatic research collector is running now.
The proposed known-source review is Monday, Wednesday and Friday at 10:00 America/Los_Angeles. Reviews can produce no changes; every finding and update is public at the same time it reaches a private workspace. Failed or missed checks are recorded honestly and checks older than seven days are labelled stale. Holiday and closure handling must be disclosed before a sale.
Proposed support hours are Monday–Friday, 09:00–17:00 America/Los_Angeles, excluding disclosed closure dates. Acknowledge requests within one staffed business day and give an assessment or next step within two. Complex cases receive a next update time; these targets are not a guarantee of a fix or emergency support. Source corrections and removal reports receive private review before changing public records.
Service-failure refund proposal
The proposed initial policy offers a full USD 19 refund when a verified settled charge has not provisioned a workspace within 24 consecutive hours, our paid workspace is inaccessible for 24 consecutive hours during its active period, or the operator cannot complete the promised 14-day service. Zero matches or unchanged sources alone are not a service failure. Other requests receive individual review without removing rights that applicable law preserves.
Refunds require a verified original payment and an exact owner-reviewed confirmation; a customer request alone never issues money. Local controls suspend access during pending or partial refunds and open disputes, revoke it after a full refund or lost dispute, and require fresh independent proof before a won dispute can restore the original unexpired period. Deleted access is not restored. These are historical proposed conditions, not the current refund policy or a statement of current availability. No renewal needs cancellation.
Recovery, privacy and retention
Anyone holding a recovery capability can retrieve its private order and workspace. Save it privately. Never put it in a URL or send it, a payment credential, card details, or a provider secret to support. A public order ID is not proof of ownership. The application stores a hash of the key, while an optional device setting keeps ownership locally. Private criteria and retrieval state do not enter the public dataset.
The retention draft proposes removing criteria and seen-state 30 days after expiry or revocation, with limited documented legal/security holds, and reviewing minimized transaction/receipt and anti-replay records after 12 months. New-workspace private export, confirmed deletion and a bounded manual retention sweep are implemented locally. Deletion immediately denies access; a response identifies any documented hold and retained minimum financial evidence. No scheduled erasure is running, financial records are not automatically purged, and the retention schedule still needs review and staffed adoption before it is an active service promise. The complete draft explains the limits.
What remains before a customer can buy
Confirm the legal seller and service address, eligible markets, tax treatment, required disclosures and final terms. Assign primary and backup staff for the next 14-day calendar, verify support delivery, and rehearse refresh, retention and remedy handling. Approve a new final live terms version, verify production payment/refund permissions, and complete the exact release, CI and cloud checks. Core checkout, recorded consent, capacity, privacy and remedy controls are implemented locally; they do not establish those business and operating facts. Separate deployment and live-sales approval is still required. This page has no accept or purchase action.
For the earlier test order, use your saved recovery file with existing test-order recovery. Do not create another payment to investigate an uncertain response. The published House contact route is for private support; its Help Map staffing and inbox delivery are not newly verified here.