Skip to app details
Back to app library
APPNEURAL APP FAMILYContent & Files

Proofs

Feedback on the exact frame, approval on the exact version

Share designs, PDFs and videos with clients, collect comments on the exact spot, and get each version approved.

01 / OVERVIEW

See where it fits in your day.

Each proof (title, project, client, deadline) holds versions v1, v2 and on: images (PNG, JPG, WebP, SVG up to 40 MB), PDFs (up to 60 MB, shown page by page in the browser) and MP4 or WebM videos (up to 95 MB) in R2, checked by extension and first bytes with a SHA-256, or a video link; files can also come in from a Creatives or Drive link. Comments are pinned at a point on an image or PDF page, or at a video time with frame stepping, with box, arrow and freehand markup, threaded replies, resolve and reopen, and @mentions. Two image versions compare side by side or with a slider. Reviewers open /p/<token> in the domain's brand with their name and email (and an email code when the proof asks for one), comment and draw on the current version, and approve or request changes; each decision records who, which version and its file SHA-256. Comment emails go out in batches every 15 minutes, with deadline reminders daily at 10:00 IST. Claude turns open comments into a numbered change list and proofreads the visible text of an image or PDF. "Record in Approvals" (optional) sends a version to Approvals; POST/GET /api/v1/proofs and webhooks.

A LOOK INSIDEExample layout · sample content
Review
T
Version 2Homepage banner
3 open comments
Approved by the client
02 / CAPABILITIES

Built around the work you do.

What Proofs does for you.

01

Pinned comments

Comments on a point of an image or PDF page, or at a video frame, with markup and replies.

02

Versions

v1, v2 and on, with side-by-side and slider compare for images.

03

Client decisions

Reviewers approve or request changes, recorded with the version and its file fingerprint.

03 / GETTING STARTED

Start small. Build from there.

A suggested path for Proofs. What you can do depends on your access in the app.

01

Upload a version

An image, PDF or video, or a link from Creatives or Drive.

02

Share the review link

Clients comment in the brand's look, with an email code if you want one.

03

Get the decision

Approve or request changes per version, with reminders before the deadline.

YOUR NEXT MOVE

Make Proofs part of your workflow.

The app opens in a new tab, so your ecosystem stays close.

Open app
05 / CATALOG DETAILS

The registry record.

Live host, inventory, governance, health checks, verification, dependencies and history.

Catalog surfaceDEPLOYEDHEALTHY
InventoryACTIVE1 items
P2VERIFIEDPUBLISHED
Overview

Purpose and boundaries

Each proof (title, project, client, deadline) holds versions v1, v2 and on: images (PNG, JPG, WebP, SVG up to 40 MB), PDFs (up to 60 MB, shown page by page in the browser) and MP4 or WebM videos (up to 95 MB) in R2, checked by extension and first bytes with a SHA-256, or a video link; files can also come in from a Creatives or Drive link. Comments are pinned at a point on an image or PDF page, or at a video time with frame stepping, with box, arrow and freehand markup, threaded replies, resolve and reopen, and @mentions. Two image versions compare side by side or with a slider. Reviewers open /p/<token> in the domain's brand with their name and email (and an email code when the proof asks for one), comment and draw on the current version, and approve or request changes; each decision records who, which version and its file SHA-256. Comment emails go out in batches every 15 minutes, with deadline reminders daily at 10:00 IST. Claude turns open comments into a numbered change list and proofreads the visible text of an image or PDF. "Record in Approvals" (optional) sends a version to Approvals; POST/GET /api/v1/proofs and webhooks.

Creative review for a connected domain: image, PDF and video versions with pinned and time-coded comments, version compare and client approval per version.

Making the design belongs to Creatives; storing files belongs to Drive; generic sign-offs belong to Approvals.

Priority
P2
Portfolio
Content & Files
Capability
Content & Files
Technical owner
Not configured
Runtime
Cloudflare Workers / OpenNext
Last verified
2026-11-18 14:03:13
Semantic inventory

Every number says what it counts

1Catalog itemstrackedEntityCount · catalog-api:live
Production-ready gate

Governance evidence required

5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.

MissingBusiness owner
MissingProduct owner
MissingTechnical owner
MissingMaintaining team
MissingGitHub repository
ConfiguredProduction URL
ConfiguredHealth endpoint
MissingDocumentation
MissingArchitecture document
MissingCurrent security review
ConfiguredData classification
MissingDependencies
MissingConsumers
MissingSLA / SLO
MissingOn-call
MissingLast release
ConfiguredLast verification
ConfiguredDeprecation status
Catalog details

proof schema v1

Catalog-specific metadata is not configured.
Live host

Where it runs

proofs.appneurox.com DEPLOYED

proofs.appneurox.com

Worker
proof-catalog
Health
HEALTHY
Last deployment
2026-11-18 14:03:13
DNS & routing

Confirmed infrastructure only

Provider inspection appears after Cloudflare credentials are configured. Mutations require dry run, idempotency and explicit confirmation.
Repository & architecture

Technical context

APPNEURAL-Catalogs/proof-catalogLOCAL · NOT CONFIGURED

Documentation

Documentation and architecture evidence are not configured.
Dependencies

Registered relationships

No dependency edges are registered. Nothing has been inferred.
Operations

Checks and verification

No health checks have been recorded.
Security

Review posture

Security review not configured. This does not mean the catalog is secure or insecure.
Automatic reconciliation

GitHub · Cloudflare · DNS · catalog APIs

No synchronization run has completed yet. The scheduled Worker records missing credentials as Not configured, never as success.

Drift findings

No drift has been recorded.
Evidence & history

Trust record

Verification is verified. Run verification to store check-level evidence, confidence, expiry and remediation.

AI workspace

Human-reviewed drafts

AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.

App libraryOpen app