On this page
A filed agreement separates holding from release
A signed agreement dated 5 November 2007 names 22THEN/Protexx as supplier, WidePoint as user and Foley & Lardner as escrow agent. It calls for source/software deposits and updates. Release involves a sworn written statement (affidavit), notice and a possible hold if the supplier disputes the request. These are historical private terms, not proof that deposit or release occurred.
The business inference is that a clause promising escrow, a deposit receipt and a usable support package answer different questions. Read the actual current agreements and verification scope rather than assuming the custodian has tested the software.
Ask for separate evidence instead of one assurance
Use an authorised rehearsal and the actual contract boundaries. Do not request live release or access merely to test a business-plan assumption.
| Record | Question it answers |
|---|---|
| Deposit/update evidence | Which exact materials and version are held, and when were they updated? |
| Release/use route | Who may request release, what evidence/notice/dispute process applies, and what use is permitted? |
| Verification result | What was actually checked—identity, completeness, build, operation—and what was excluded? |
| Continuing service | Who supplies tools, permitted licences, knowledge and updates after a valid release? |
A recent receipt can still describe the old supported version
Fictional example: the customer runs release 4.2. The escrow receipt is recent but identifies release 4.0, and the verification report only checked file presence. Those facts do not establish that a replacement team can build or support 4.2.
Have the authorised parties reconcile the deposited version and the promised verification. Price any permitted update or expanded test. The exercise is about the escrow commitments and evidence, not a procedure for restoring a customer’s live machine.
Approve the fallback you can substantiate
Ask management to show the material scope, update owner, actual release/use permissions, verification limits and cost of maintaining the arrangement. A supplier’s failure does not by itself establish that your chosen release condition is satisfied.
If the evidence falls short, investigate a better-supported arrangement, another permitted continuity route or a narrower service promise. Keep private source, credentials, release notices and agreements in the appropriate restricted systems.
Scope
- Historical filed agreement and an original preparation exercise. No current release trigger, use permission, insolvency outcome, agent verification duty or support guarantee is established.
Next step
Use Partner evidence to record the supplier’s escrow claim, exact evidence checked and its limits. Keep deposits, agreements and tests in your own authorised systems.
Sources & review notes
WidePoint Corporation — SEC-filed Exhibit10.4
Passage, dates and research notes
company-filed-agreement · Complete 3-page agreement/signatures; selected clauses 1–4 and 6–8
Direct HTTP 200 body retained and fully read. Historical private agreement, not current law or proof of deposit/release; signatures include 5/7 November 2007. No EXAMPLE ONLY form is used.
Bookmark this guide or mark it as read.
Progress privacy
Saving is off by default. Without it, progress lasts only on this page. If you turn it on, this browser profile stores public content IDs and the progress you record. Anyone sharing the profile could see them. No plan inputs or contact details are included. Reset or export in learning settings.
This is a reading aid, not evidence of disclosure delivery, expertise or legal approval.