Trust
Cenelira is a controlled publishing system for social posts. It refuses ambiguous destinations, binds approvals to the exact version reviewers saw, classifies failures with a typed cause, and produces a signed proof record per schedule. This page lists the mechanics that ship today, the support path, and the explicit set of claims that Cenelira does not make.
Every claim below maps to imported repo constants or files named in code on a linked mechanic page. No customer logos, no aggregate ratings, no fabricated testimonials, no ranked competitor comparisons.
Cenelira schedules, validates the destination, binds approval to the exact version, classifies failures, and produces a signed proof record per schedule. The output is a provable workflow record, not a throughput number.
Agency operators running multi-platform publish queues for clients; brand teams who need a reviewable record of who approved what version on which destination, and what actually happened at publish.
Today Cenelira ships the mechanics linked from this page. It does not claim SOC 2, ISO 27001, HIPAA, GDPR certification, audience guarantees, or compete on customer logos.
Entity
Three facts ground the rest of the page. The product name and support contact are constants in src/lib/brand.ts. The declared scope is the union of every public mechanic page on this site.
Cenelira
Controlled scheduling, approvals, publishing, recovery, and signed proof export across the public platform inventory: Instagram, Facebook, Threads, LinkedIn, YouTube, TikTok, Pinterest, X.
What ships
Each link below names a typed mechanism that runs in the publish path or the export pipeline. The depth pages name the exact code that enforces the behavior, so this page is a directory rather than a duplicate.
Six typed publish-path refusals when the persisted destination account is missing or invalid. Each refusal returns HTTP 409 target_repair_required.
External review decisions are bound to the schedule's SHA-256 reviewVersion fingerprint. Edits between link issue and decision commit reclassify the link as SUPERSEDED.
Twenty-one typed publish-failure causes mapped to nine typed next actions and six typed owner kinds. Replay is offered when the cause and replayability gate allow it.
The typed manual-completion workflow that runs when a schedule's publishMode or status equals HANDOFF. Seven typed reasons; two states (pending, completed).
A 17-field record per schedule, exported as a signed PDF or an unsigned CSV twin. HMAC-SHA256 over the canonical payload of the signed PDF; the signing secret is never embedded in the artifact.
Who this is for
Cenelira adds value where an approval that means "yes to the version I read" differs from an approval that means "yes in general," and where a failure without an owner is unacceptable. It adds less value when the team needs a high-volume queue with no audit responsibility.
Proof artifact
Every shipping mechanic above ends in the same place: a row in the signed 17-field proof record. The signed PDF and the unsigned CSV twin both carry every column, a verifier can recompute the HMAC-SHA256 signature from the canonical payload of the signed PDF, and the signing secret is never embedded in the artifact.
The proof export records scheduleId, versionFingerprint, targetAccount, platform, publishAtISO, approverIdentity, approverSource, approvalTimestamp, invalidationReason, publishOutcome, publishedAtISO, platformPostId, exceptionCause, recoveryAction, recoveryActor, deliverySetId, and deliverySetMemberCount.
The verification recipe lives on the proof page: copy the canonical payload, recompute the SHA-256 digest, then recompute HMAC-SHA256 with the shared signing secret and compare it against the printed signature.
The proof export does not claim audience, reach, or authenticated identity for external reviewers. It records typed workflow state and platform response.
Support
Support runs by email at [email protected]. Cenelira does not advertise round-the-clock coverage, instant response SLAs, or dedicated success managers. Procurement requirements that need a vendor questionnaire, a security packet, or a data processing agreement are answered per-engagement on the same address.
Public limitations
These are not refusals to ship. They are the honest edges of mechanics that already run in the publish path or in the export pipeline.
External reviewers approve via a review link. Their identity is self-declared, not authenticated. Only internal workspace approvals are tied to a workspace user account.
No part of the proof export, the recovery surface, or any public claim on this site describes audience, delivery, or reach. The proof record reports platform response and workflow state, not impressions.
Wrong-account prevention runs at publish time on schedules created in Cenelira. It does not retroactively audit posts that predate the connection.
Every supported platform has an auto-publish path. LinkedIn multi-image currently routes through the typed manual handoff path. Handoff packs records who completed the manual publish; it is not a permanent platform limitation.
No public claim today for SAML SSO, SCIM provisioning, audit-log retention SLAs, or workspace data residency selection. Procurement requirements are handled directly by email.
Does not claim
Vendors in this category often ship the language below as ornament. Cenelira ships the absence on the public surface, so no procurement reviewer has to ask twice.
Cenelira does not claim SOC 2, ISO 27001, HIPAA, or GDPR certification. The trust layer that ships is the typed publish-path refusals, version-bound approvals, owned recovery, and signed proof export named on this page.
Cenelira does not promise reach, delivery, engagement, or any audience outcome. The publish path either succeeds with a platform post id, refuses for a typed reason, or is recorded as a typed failure.
No customer logos, no fabricated testimonials, no aggregate ratings, no review schema. The public surface ships what is true today, not what would look impressive.
Cenelira does not publish ranked comparisons against named competitors. The mechanics pages on this site describe what Cenelira does, named in code.
Support runs by email at [email protected]. Cenelira does not advertise round-the-clock coverage, instant response SLAs, or dedicated success managers.
Unknown / deferred
A careful reader of a trust page might expect each item below to be declared. Cenelira has chosen not to invent values for them on the public surface. Each row says what is missing and where to ask.
The legal entity name, registration jurisdiction, and postal address are not declared on the public surface today. Procurement contacts that require this information should email [email protected].
Cenelira does not publish sameAs links to social profiles, press pages, or public registries. The Organization JSON-LD on the trust and home pages carries no sameAs array.
Vendor questionnaires, security review packets, and data processing agreements are handled per-engagement by email rather than published as static downloads on this site.
FAQ
Cenelira is a controlled publishing system for social posts: it refuses ambiguous destinations, binds approvals to the exact version, classifies failures with a typed cause, and produces a signed proof record per schedule.
Cenelira is built by a small team. The legal entity name, registration jurisdiction, and postal address are not declared on the public surface today; procurement questions go directly to [email protected].
Support runs by email at [email protected]. Cenelira does not advertise round-the-clock coverage, instant response SLAs, or dedicated success managers.
The signed proof archive is the export. Each proof record carries 17 fields, including approval, target account, platform, publish outcome, exception, recovery, and delivery-set columns. The signed PDF and the unsigned CSV twin both leave the app, and the verification recipe for the signed PDF is published on the proof page.
No public claim today for SOC 2, ISO 27001, HIPAA, or GDPR compliance attestations. The trust layer that ships in Cenelira is the typed publish-path refusals, version-bound approvals, owned recovery, and signed proof export named on this page.
Cenelira supports controlled scheduling and publishing workflows across eight platforms with an auto-publish path on each: Instagram, Facebook, Threads, LinkedIn, YouTube, TikTok, Pinterest, X. LinkedIn multi-image currently routes through the typed manual handoff path documented on the handoff packs page.
No. External reviewer identity on a Cenelira review link is self-declared. Internal approvals are tied to workspace user accounts; the version-bound approval page describes how decisions are bound to the SHA-256 reviewVersion at decision commit.
Every claim on this page maps to imported repo constants or files named in code on the linked mechanic pages. The page carries a last-reviewed stamp; when a mechanic ships or its scope changes, the corresponding facts file and link are updated, and the stamp is bumped.
Last reviewed 2026-04-25
