Category
Engagement
Reader views, reads, reactions, ratings, comments, and members
Engagement
Reader engagement for everything Vlozi publishes: view and read counts, reactions and star ratings, comments with moderation, and passwordless reader identity. One service, one gen
Engagement — API Reference
| Class | Auth | Tenant from | |---|---|---| | /e/ | none — public door | the eng_sites row the site_id points at | | /admin/ | gateway key + JWT/API key + requirePermission | x-te
Engagement — Architecture
browser tenant's blog │ no credential — opaque site_id in the path ▼ gateway /engagement/e/ ──── CORS registered BEFORE the rate limiter │ BEACON_RATE_LIMITER, path-scoped ▼ engage
Engagement — Backlog
These are not code changes — they're steps someone has to take before the built code does anything. | | What | Why it's blocking | |---|---|---| | D1 | wrangler.toml is gitignored
Engagement — Billing
| Action | Cost | Reason code | Mechanism | |---|---|---|---| | A comment becomes published | 0.1 credit ENGAGEMENT_COMMENT_THOUSANDTHS: 100 | engagement.comment.publish | Accumula
Engagement — Database
| Table | Primary key | Holds | |---|---|---| | eng_sites | id | one embeddable surface per tenant: origins, Turnstile key, status | | eng_settings | tenant_id | every tenant-level
Engagement — Embedding
Three ways to put engagement on a site. All three talk to the same public door, and all three need only a site_id — never an API key. | | Use when | |---|---| | React SDK @vlozi/bl
Engagement Service — Implementation Plan
--- - §1 Context, §2 Bugs/gaps/improvements found, §3 Conventions the rules every file must follow, §4 Phases 0–14 each: goal, files, exact edits, tests, exit criteria, §5 Permissi
Engagement — Permissions
Defined in packages/core-access/src/permission-catalogue.ts. Owner, admin and viewer roles derive from it automatically; nothing hardcodes a role's engagement permissions. | Permis
Reader Engagement — Vision & Architecture
--- - Tenants asked for view counts, ratings and comments on their blog posts. Blog today is read-only and the platform has no concept of a "reader", so there is nothing to extend