> For the complete documentation index, see [llms.txt](https://docufi3d.gitbook.io/docufi3d/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docufi3d.gitbook.io/docufi3d/technical-documentation/core-process.md).

# Core Process

<figure><img src="https://1270204656-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3rNBjnk1QooV43GjCjYX%2Fuploads%2FmNaaWCw8n9Y7IdGlwgkD%2FDocufi3d%20-%20Core%20Process.png?alt=media&amp;token=97868a06-d21a-4c12-a6f5-abd1a9dbc9fc" alt=""><figcaption></figcaption></figure>

### 🔁 Docufi3d Core Process – Summary

The Docufi3d platform enables users to securely upload, prepare, invite, and digitally sign documents. The process includes automatic text extraction, payment handling, and final sealing on the Cardano blockchain.

***

#### 🟩 1. Login & Dashboard

1. **Login:**\
   The user logs into the Docufi3d platform.
2. **Dashboard:**\
   After login, the user is directed to the main dashboard, where document actions begin.

***

#### 📄 2. Upload & Document Preparation

3. **Upload:**\
   The user uploads a document for signing.
4. **Check if PDF:**
   * If not a PDF → Convert to PDF
   * If already PDF → proceed to text check
5. **Check for Text Layer:**
   * If missing → Text is extracted
   * Text layer is added to make the PDF machine-readable

***

#### ✉️ 3. Invitation Flow

6. **Invite:**\
   The user adds one or more signers and sends an invitation.
7. **Place Signature Fields:**\
   The initiator defines where signatures should be placed in the document.
8. **Payment:**
   * A pay-per-use payment is made
   * System supports toggling between free access and active billing
   * Generates an **Invite Email** to notify the signer

***

#### ✍️ 4. Signing & Sealing

9. **Sign:**\
   The invited party accesses the document and signs it.
10. **Check for Last Signature:**

* If this is the final required signature:
  * A **Signature & Status Email** is sent
  * The document is **sealed (PDF)**
  * A **Cardano transaction** records the signature proof
  * A **Confirmation Email** is sent to all parties
* If not the final signature → return to dashboard / wait for next signer

***

#### 🔄 5. Loops & Navigation

* Users can return to the dashboard at several points (after invite, signing, or completion)
* The platform ensures all documents are text-readable before inviting
* Email triggers are used for:
  * Signer invitations
  * Status updates
  * Final confirmation after blockchain seal

***

#### ✅ Key Functional Highlights

* **OCR-based text detection and layer injection**
* **Flexible invite and signer management**
* **Integrated payment before signature initiation**
* **Blockchain anchoring of sealed PDFs on Cardano**
* **Automated notification system throughout the process**


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docufi3d.gitbook.io/docufi3d/technical-documentation/core-process.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
