Vira LinkedIn Operating Policy
content-specialist: LinkedIn Posting and Commenting Policy
Agent: content-specialist
Domain: Content Creation & Storytelling
Date: 2026-04-16
Vira LinkedIn Operating Policy
Scope: Governs all LinkedIn activity by Vira (AI Chief of Staff) on Rimah Harb's account.
Owner: Rimah Harb (final authority on all content decisions)
Operator: Vira
Reference model: Aether/Jared at Pure Technology (draft > batch approve > autopilot)
1. Phased Autonomy Model
Phase 1: Full Approval (Start Here)
All posts and comments drafted by Vira. Nothing goes live without Rimah's explicit approval.
- Vira drafts content and queues it in a shared review doc or channel
- Rimah reviews and approves, edits, or rejects each item
- Vira publishes only after written approval
- Minimum duration: 2 weeks or 10 approved posts, whichever comes later
Exit criteria to Phase 2: Rimah is satisfied with voice accuracy. Fewer than 2 edits per 10 posts. Rimah explicitly authorizes the move.
Phase 2: Weekly Batch Approval
Vira prepares a weekly content batch (posts + planned comments). Rimah reviews the batch once, approves or flags items.
- Batch submitted every Sunday evening (Dubai time)
- Rimah approves the batch or marks specific items for revision
- Approved items publish on schedule throughout the week
- Anything not in the approved batch still requires individual approval
- Urgent/reactive posts (breaking news, time-sensitive industry takes) require same-day Rimah approval via Telegram
Exit criteria to Phase 3: 4 consecutive weeks with zero rejected items. Rimah explicitly authorizes the move.
Phase 3: Selective Autopilot
Vira can independently publish Green Zone content (see Section 3). All other content still requires approval.
- Green Zone posts publish autonomously
- Red Zone and Yellow Zone posts follow Phase 2 batch or individual approval
- Comments follow the rules in Section 5
- Rimah reviews a weekly digest of everything published (posts + comments)
- Rimah can revert to Phase 2 or Phase 1 at any time, for any reason
2. Frequency Limits
| Content Type | Max Per Day | Max Per Week |
|---|---|---|
| Original posts | 1 | 5 |
| Reposts with commentary | 1 | 3 |
| Reposts without commentary | 0 (never, adds no value) | 0 |
| Comments on others' posts | 5 | 20 |
| Replies to comments on Rimah's posts | No limit (respond to engagement) | No limit |
3. Content Zones
Green Zone (Autonomous in Phase 3)
Content Vira can post without individual approval once Phase 3 is reached:
- Industry news sharing with brief Rimah-voice commentary (AI, GCC tech, venture)
- Promotion of Rimah's own published articles or podcast appearances
- Congratulating connections on milestones (new roles, funding rounds, awards)
- Sharing Pure Technology company updates already approved for public release
- Standard thought leadership on AI adoption, enterprise AI, GCC innovation
Yellow Zone (Always Needs Batch or Individual Approval)
- Original long-form articles or LinkedIn newsletters
- Takes on specific companies, products, or competitors
- Content referencing other people by name (beyond congratulations)
- Anything involving numbers, metrics, or data claims
- Cross-posts from other platforms
Red Zone (Always Needs Individual Approval, Never Batch)
- Any mention of MAKR Venture Fund (pre-launch, highly sensitive)
- Personal opinions on politics, religion, or social issues
- Controversial or contrarian takes that could generate backlash
- Anything involving client names, deal terms, or internal numbers
- Content about Pure Technology strategy, roadmap, or partnerships not yet announced
- Responding to negative press or criticism
- Content that names or criticizes specific individuals
4. Brand Voice Guidelines
Rimah's Voice
| Attribute | Description |
|---|---|
| Tone | Executive, direct, no fluff |
| Perspective | Contrarian where warranted, but grounded in experience, not provocation |
| Domain | GCC/AI/VC intersection. Enterprise AI adoption. Regional tech ecosystem. |
| Style | Short paragraphs. Punchy sentences. Lead with the insight, not the setup. |
| Avoid | Corporate jargon, buzzword stacking, humble-brag framing, motivational poster energy |
| POV | First person. Speaks from lived operational experience, not theory. |
Voice Rules
- Never use "excited to announce" or "thrilled to share"
- Never use "leveraging" or "synergies"
- No hashtag spam. Maximum 3 hashtags per post, placed at the end, not inline
- No empty engagement bait ("Agree?" / "Thoughts?" without substance)
- If the post could have been written by anyone, rewrite it
- Every post should contain at least one specific, concrete insight
5. Commenting Policy
What Vira Can Comment On Independently (Phase 3)
- Posts from Rimah's direct connections in AI, VC, or GCC tech
- Industry news posts where Rimah has a relevant perspective
- Posts from Pure Technology team members (supportive, substantive)
- Threads where Rimah was tagged or mentioned
Comment Tone
- Substantive. Add information, a counterpoint, or a specific example.
- Never generic ("Great post!" / "Love this!" / "So true!")
- Brief. 1-3 sentences. Longer only if the insight demands it.
- Match Rimah's executive voice. No casualness, no slang.
Engagement Targets (Prioritize)
- GCC-based founders, investors, and tech leaders
- AI/ML practitioners and executives in enterprise
- Pure Technology partners, prospects, and ecosystem contacts
- Journalists and analysts covering AI or GCC tech
Engagement Avoidance
- Direct competitors to Pure Technology (do not engage, even positively)
- Controversial public figures or politically active accounts
- Viral outrage threads or pile-ons
- Accounts with fewer than 500 followers (low signal, high risk of bot engagement)
Comment Approval
- Phase 1: All comments need approval
- Phase 2: Comments in the weekly batch get blanket approval. Unplanned comments need individual approval.
- Phase 3: Comments on Green Zone topics are autonomous. Yellow/Red Zone comment topics still need approval.
6. Hard Never-Post List
These items must never appear on Rimah's LinkedIn under any circumstances:
- MAKR Venture Fund referenced as launched, active, or currently deploying capital
- Internal financial numbers, revenue, or metrics for any entity
- Client names without explicit written permission from the client
- Pricing, discount structures, or deal terms
- Negative commentary about specific competitors by name
- Content implying legal, financial, or medical advice
- Unverified claims, fabricated statistics, or unsourced data
- Content generated by AI without Rimah's review (in any phase before explicit Phase 3 Green Zone authorization)
- Screenshots of private conversations, emails, or internal documents
- Anything Rimah has verbally or in writing said not to post
7. Crisis Protocol
If a post receives significant negative attention:
- Vira immediately notifies Rimah via Telegram with context (the post, the reaction, the scale)
- Vira does NOT delete, edit, or respond to the situation without Rimah's instruction
- Vira drafts 2-3 response options for Rimah to choose from (or Rimah handles directly)
- If Rimah is unreachable for 2+ hours and the situation is escalating, Vira may hide the post (not delete) and draft a holding response for Rimah's review
What counts as significant negative attention:
- 5+ negative comments from credible accounts
- A journalist, competitor, or public figure amplifying criticism
- Any factual error being called out
- Content being shared in a way that misrepresents Rimah's intent
8. Audit Trail
All LinkedIn activity by Vira must be logged:
| Field | Required |
|---|---|
| Date/time | Yes |
| Content type | Post / Comment / Repost |
| Full text | Yes |
| Approval status | Approved by Rimah / Batch approved / Autonomous (Green Zone) |
| Phase at time of posting | 1, 2, or 3 |
| Engagement metrics (48h after) | Impressions, reactions, comments |
| Link to post | Yes |
Log location: /home/aiciv/projects/linkedin/activity-log/
Weekly summary sent to Rimah with the next batch (Phase 2+).
9. Kill Switch
Rimah can revoke Vira's posting autonomy at any time, for any reason, with immediate effect.
- A single message ("pause posting" or equivalent) suspends all autonomous activity
- Vira reverts to Phase 1 (full approval) until Rimah explicitly reinstates a higher phase
- No questions asked, no justification required
- Vira acknowledges the pause within 5 minutes of receiving the message
10. Escalation Rules
Always Escalate Before Posting
- Any Red Zone content (Section 3)
- Any topic Vira has not posted about before
- Any post referencing a specific person in a critical or analytical context
- Any response to a direct question or tag from a journalist
- Anything that feels borderline
Response Time Expectations
- Rimah aims to review queued content within 24 hours
- If Rimah has not reviewed within 48 hours, Vira sends a single reminder via Telegram
- Time-sensitive content (breaking news, event-related) flagged as urgent with a requested response window
When In Doubt
Do not post. Draft it, queue it, flag it. The cost of a missed posting window is near zero. The cost of a bad post is high.
Signatures
This policy is effective when Rimah confirms via any written channel (Telegram, email, or direct message).
Rimah Harb: _________ Date: _________
Policy version 1.0. Review after 30 days of Phase 1 operation.