# Fictional recipient visibility model This original teaching example separates invitation order, field visibility and edit permission. It is not the implementation of Docusign, Adobe or any other provider. Its rules are deliberately declared in the code. Nothing is signed, sent, uploaded, stored or fetched. ## Run Use Node.js 24.19.0, then run from this directory: ```sh node recipient-model.mjs > results.json ``` The six assertions stop the run if an expected result differs. The saved results.json records the actual UTC date and runtime. Reruns change the timestamp; compare the six cases, not the whole output hash. This program uses only Node's built-in assertion module. No install, credentials or network access is required. ## Limits The cases do not test a real service, document rendering, authentication, provider roles, signature validity, conditional-field UI or the effect of altering any agreement. They illustrate questions an authorized sender can check using a fictional draft in their own approved system. The program neither authorizes a change nor decides who should sign. Original code: MIT. Original observation data in results.json: CC BY 4.0. Provider documentation is not included.