Help with Ariavel Seal

What is Ariavel Seal?

Ariavel Seal is an approval integrity app being built for monday.com. It is designed so that a person confirms the exact values of the fields that matter, and Ariavel Seal records that confirmed state as a seal. If a protected value later changes, Ariavel Seal is designed to mark its own seal as broken and show exactly what changed. This behaviour has been shown only in the local validation prototype, not yet in monday.com.

It is an integrity layer for workflows where post-approval changes matter, such as an approved amount, deadline or scope. It is not a row-locking tool, it does not change the monday.com Approved status, and it is not a legal electronic signature.

Getting started Requires validation

Ariavel Seal is not yet available for installation, and there is no monday.com Marketplace listing yet. You cannot add it to a monday.com account today.

To hear about early access, email support@ariavel.eu with the subject “Ariavel Seal early access” and a short description of the approval workflow you want to protect. Installation and onboarding steps will be published here when they exist.

Create a Seal policy Prototype

A policy tells Ariavel Seal what approval protects on a board. It names:

• the board it applies to;
• the approval prerequisite, for example the existing Approved status label, which makes an item eligible for review;
• the protected fields whose values a reviewer confirms.

Saving a changed policy creates a new policy version. Seals confirmed under the previous version keep their original definition in history and are not treated as valid for the new version.

Choose protected fields Prototype

Choose only the fields whose approved values matter, such as an amount, a deadline, a scope description or a risk status. Only selected fields are part of the confirmed state. Changes to other fields do not affect the seal.

During validation, protected fields must use a supported field type. See Supported fields during validation.

Review protected values Prototype

When an item meets the approval prerequisite, it becomes eligible. Approved status alone does not create a seal. The reviewer selects Review protected values and sees the exact current values of every protected field.

A review is valid for a short time. If it expires, start a new review.

Confirm & Seal Prototype

Selecting Confirm & Seal records a seal for the exact values the reviewer saw. Before it records the seal, Ariavel Seal reads the values again. If any protected value changed since the review, nothing is sealed and the reviewer is asked to review the new values.

The seal includes a checksum of the confirmed state. The checksum identifies that state for comparison; it is not a legal digital signature.

✓SEALED What it means Prototype

The current protected values match the state a person confirmed, and the latest check succeeded. A positive result is shown only after a recent successful check. When that check is no longer recent, the item shows Verification Required until it is checked again.

!SEAL BROKEN What it means Prototype

A protected value changed after confirmation. Ariavel Seal marks its own seal as broken; it does not change the item or its monday.com status. A new human review is required.

A broken seal stays broken even if the value is later changed back. The item then shows the note “Current values match again. This seal remains broken.”

Understanding the exact diff Prototype

The comparison lists each changed protected field with its confirmed value and its current value. Example with fictional data:

Numbers are compared exactly, without rounding, and the numeric difference is shown. Text is compared exactly, including spaces and capitalisation, so two values that look alike can still differ. Dates are compared as calendar dates.

The comparison is deterministic: the same confirmed and current values always produce the same result.

Reapproval Prototype

When a seal is broken, select Review for reapproval, check the current values and select Confirm & Seal. This creates a new seal for the newly confirmed state. The previous seal is marked as superseded and kept in history with its original values.

Ariavel Seal never reapproves anything on its own.

History Prototype

History lists each seal and what happened to it in order: created, broken, observed changes, superseded and the new seal that replaced it. It helps a team understand which state was confirmed and what replaced it.

History is a product record, not certified audit evidence.

?VERIFICATION REQUIRED What it means Prototype

Ariavel Seal could not safely establish positive integrity, so it does not show the item as sealed. A matching value on its own is not enough. You may see this when:

• the latest check could not be completed;
• the last successful check is no longer recent;
• Ariavel Seal cannot confirm whether protected values changed in between;
• the protected field setup changed after confirmation.

Select Verify now to check again. SEALED can return only when the item is still eligible, the protected values match, there is enough evidence to verify integrity, and the seal is still valid. A broken or revoked seal needs a new review; matching values alone never repair it.

Supported fields during validation Requires validation

Validation deliberately covers a limited set of ordinary item fields:

• Text
• Numbers
• Dates without a time
• Status
• Checkbox

The Draft preview distinguishes an observed empty field, shown as Not set, from a number equal to zero or an Unchecked checkbox. Text containing meaningful whitespace is still a value; exact character details help explain otherwise invisible differences. Text such as “Empty” is ordinary text, not a cleared field.

These representations are being checked with fictional data on monday.com. Recognizing an empty field does not establish a seal: confirmation, current access and monitoring must also be verified. Unrecognized or contradictory field data requires verification.

Formula, mirror, connected-board, people, dropdown, file, timeline, subitem and other field types are not supported. An item with an unsupported or incomplete value is never shown as sealed.

Permissions and access Requires validation

In the prototype, only account admins can save a policy, and only people configured as approvers can confirm or reapprove a seal. Guests and view-only users cannot confirm.

View-only monday.com accounts cannot use the API. Ariavel Seal explains this access limitation and keeps protected values unavailable in that session.

How this maps to monday.com roles, board access and private boards requires validation on the real monday.com platform. The rules will be documented here before public installation.

Security and privacy boundaries Requires validation

To show an exact comparison later, Ariavel Seal keeps the protected values a person confirmed, together with the seal history. It is designed to keep only the selected protected fields, not whole boards, updates or unrelated columns.

An Ariavel Seal Privacy Policy and Terms of Service, including data retention and deletion, will be published before public installation. The validation prototype uses fictional data only. To report a security issue, email security@ariavel.eu.

AI and Seal validity Prototype

By design, Seal validity is deterministic. Ariavel Seal compares the confirmed and current protected values exactly. AI does not decide whether a seal is valid, does not confirm or reapprove, and does not change your data. The validation prototype contains no AI features.

Connection and OAuth Requires validation

The current Draft can read its dedicated test board as the signed-in viewer. Server verification and background connection are separate prerequisites; a working read does not mean saving or confirmation is ready. The Draft explains when the connection needs attention and keeps those actions unavailable.

Do not disable browser or workplace security protections to connect. Contact your administrator if a connection page is blocked. Never send an authorization code, token, browser cookie or Client Secret to support.

Monitoring and recovery Requires validation

Background monitoring is not enabled in the current Draft. Current values and historical changes are different facts: values may match again after an intervening edit. A missing event or empty history response cannot establish that no change occurred.

The intended workflow requires enough verified evidence before showing SEALED. An unavailable connection, incomplete evidence or delayed recovery must be explained as Verification Required. A proven broken seal needs a new human review even when its values match again.

Retention and uninstall Requires validation

The current validation environment uses dedicated fictional data. Customer retention periods, uninstall cleanup and independently verified deletion still require real-platform validation before release. A successful delete request alone is not proof that every retained record has been removed.

Before public installation, the product-specific privacy policy will identify what is retained, why, for how long and how removal is verified. Do not treat the local prototype history as a customer archive or a legal signature record.

Billing readiness Requires validation

Public installation and billing are not active. Early access is an expression of interest and creates no subscription or charge. The launch model must be checked against the working product, platform limits and measured capacity before commercial availability.

Any eventual Seal subscription will be separate from Ariavel Sourcing. Product integrity cannot be inferred from a pricing page or plan selection.

Troubleshooting

Confirm & Seal says the protected values changed.

A protected value changed after you opened the review. Review the new values and confirm again if they are correct.

The review expired.

Reviews are valid for a short time. Start a new review.

The review button is not available.

The item may not meet the approval prerequisite yet, or the policy may be disabled.

The seal is broken, but the values look the same.

A protected value may have been changed and then changed back, or the values may differ in a detail that is easy to miss, such as an extra space. The seal stays broken; review the current values for reapproval.

The item shows Verification Required.

Select Verify now. If it continues, contact support@ariavel.eu.

Early access FAQ

Is Ariavel Seal available now?

Not yet. It is in product validation, and early access is being prepared.

How do I join early access?

Email support@ariavel.eu with the subject “Ariavel Seal early access”.

How much will it cost?

Pricing has not been set. Plans will be published before installation becomes available. See pricing readiness. Billing and public installation are not active.

Does Ariavel Seal lock monday.com items?

No. People can keep editing items. Ariavel Seal is designed to show whether the protected approved state still holds.

Is Ariavel Seal developed or endorsed by monday.com?

No. Ariavel Seal is an independent app being built for monday.com.