Pieces and reviews
Seven kinds of piece with a brief, per-network text, pictures and video, versions and comments. A second person approves one exact version; editing it again voids the approval.
Ideas to approved pieces, by people and agents
Make the business's content in one place: ideas, drafts and reviews by people and AI agents, approved by a person and handed to Social to schedule and publish.
A piece has a kind (social post, article, newsletter, script and more), a brief, a body with per-network text, up to four pictures or one video in R2, a pillar, tags, a target date and an assignee, a person or an agent. Every real change makes a version; comments belong to a version and versions can be compared word by word. A piece moves idea, draft, review, changes, approved, handed, published, shown as a pipeline, a list and a calendar. Review needs a second person by default: an editor approves the version they read, and the approval holds that version's hash, so any later edit voids it. Agents (idea scout, writer, rewriter, checker and others) run on demand, on a schedule or from a workflow, read the pillars, the references and the brand voice from Brand Kits and Brand DNA, and can only propose: their pieces wait for a person. Workflows chain agent steps and waits for a person. Every run shows its steps and its cost against a monthly cap. Approved pieces are handed to APPNEURAL Social through a service binding with their pictures and video; Social schedules and publishes, and Content reads back what was scheduled and published. Content never talks to a social network itself.
What Content does for you.
Seven kinds of piece with a brief, per-network text, pictures and video, versions and comments. A second person approves one exact version; editing it again voids the approval.
Agents find ideas, draft, rewrite and check pieces against your references and brand voice, on demand or on a schedule. Workflows chain steps with waits for a person, and every run shows its steps and cost against a monthly cap.
Only approved pieces are handed to Social, with their pictures and video; Content shows what Social scheduled and published. Publishing and scheduling happen in Social only.
A suggested path for Content. What you can do depends on your access in the app.
Add the domain's content themes, a weekly target for each, and your references.
Write a piece, or switch on an agent or a workflow that drafts in your brand voice.
Approve the version you read, then send it to Social to schedule.
Live host, inventory, governance, health checks, verification, dependencies and history.
A piece has a kind (social post, article, newsletter, script and more), a brief, a body with per-network text, up to four pictures or one video in R2, a pillar, tags, a target date and an assignee, a person or an agent. Every real change makes a version; comments belong to a version and versions can be compared word by word. A piece moves idea, draft, review, changes, approved, handed, published, shown as a pipeline, a list and a calendar. Review needs a second person by default: an editor approves the version they read, and the approval holds that version's hash, so any later edit voids it. Agents (idea scout, writer, rewriter, checker and others) run on demand, on a schedule or from a workflow, read the pillars, the references and the brand voice from Brand Kits and Brand DNA, and can only propose: their pieces wait for a person. Workflows chain agent steps and waits for a person. Every run shows its steps and its cost against a monthly cap. Approved pieces are handed to APPNEURAL Social through a service binding with their pictures and video; Social schedules and publishes, and Content reads back what was scheduled and published. Content never talks to a social network itself.
Social owns the profiles, scheduling, publishing, the inbox and analytics; Content never talks to a social network. Brand DNA and Brand Kits hold the brand voice that Content reads; Creatives designs the pictures; Documents and Writer hold business documents that are not marketing content.
5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
contents.appneural.com
Verification is verified. Run verification to store check-level evidence, confidence, expiry and remediation.
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.