Skip to content

refactor: advocate for Holdex #70

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
zolotokrylin merged 4 commits into from
Dec 8, 2025
Merged

refactor: advocate for Holdex #70

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
ba88354
refactor
zolotokrylin Dec 8, 2025
569f4e4
refactor
zolotokrylin Dec 8, 2025
0d1320f
refactor
zolotokrylin Dec 8, 2025
b7e522a
refactor
zolotokrylin Dec 8, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
79 changes: 35 additions & 44 deletions docs/ADVOCACY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,59 +1,50 @@
# Advocacy Guidelines
# Holdex Advocacy Guidelines

If you are a Holdex team member, we expect you to advocate for Holdex, its
mission, and its values. This includes:
As a Holdex team member, you must actively advocate for Holdex, its mission, and
its values. This requires:

- Participate in community events and activities that align with Holdex's
mission and values.
- Share Holdex-related content on social media platforms, including LinkedIn and
Twitter.
- Represent Holdex professionally and ethically, and to uphold the company's
code of conduct at all times.
- Participating in aligned community events and activities.
- Sharing and engaging with Holdex content on LinkedIn and X (formerly Twitter).
- Representing Holdex professionally, ethically, and in line with our
[Code of Conduct](./CODE_OF_CONDUCT.md).

## Social Media Presence

Your Personal Social Media Presence:
Maintain a professional online presence that promotes Holdex. Upon joining,
immediately update your GitHub, LinkedIn, and X profiles to reflect your role.

- Create and maintain a professional LinkedIn profile that showcases your work
at Holdex.
- Use Twitter to share Holdex-related news, updates, and insights.
- Engage with Holdex's community on social media platforms, responding to
comments and questions.
### GitHub Profile

When you join Holdex you must update your GitHub, LinkedIn and X (formally
Twitter) profiles to reflect Holdex.
Exclusively promote Holdex in your bio while employed—no other brands or links.
Checklist:

### Profile Checklist

### GitHub Bio

While employed by Holdex, exclusively promote Holdex in your bio. Do not include
other brands or non-Holdex links..

| Github Profile Attributes | Acceptance Criteria |
|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Name | Only state your First Name |
| Bio | Describe your Role at Holdex. I.e.: “Full-stack Engineer at @holdex”> |
| Company | @holdex |
| Location | localhost |
| Time | Uncheck; don’t display current time |
| Email | Must be empty |
| Social link 1 – X | Must be: “<https://x.com/holdex.io”> |
| Social link 2 – Website | <https://holdex.io/c/jobs> |
| Social link 3 – LinkedIn | <https://linkedin.com/company/holdex> |
| Pinned Repositories | Trial |
| Overview | Create a ‘README.md’ file in public self-repo that states: role at Holdex, what you do & what you love about Holdex, link to Holdex website and GitHub organization profile. |
| Attribute | Requirement |
|-----------|-------------|
| Name | First name only. |
| Bio | Role at Holdex (e.g., "Full-stack Engineer at @holdex"). |
| Company | @holdex |
| Location | localhost |
| Time | Uncheck; hide current time. |
| Email | Empty. |
| Social Link: X | <https://x.com/holdex.io> |
| Social Link: website | <https://holdex.io/c/jobs> |
| Social Link: LinkedIn | <https://linkedin.com/company/holdex> |
| Pinned Repositories | Holdex-related only. |
| Overview | In a public self-repo, create README.md stating your role, contributions, enthusiasm for Holdex, and links to Holdex website and GitHub org. |

### LinkedIn Profile

Must mention Holdex in the ‘Experiences’ tab & place it as the recent / current
role.
Add Holdex as your current experience in the "Experience" section. Use this
mandatory description:

Mandatory `Experience` description:
> Holdex is premier partner for institutions pioneering DeFi & RWAs. Hong Kong-based since 2016, we turn bold visions into secure, scalable blockchain solutions – driving adoption with unmatched expertise.
> Holdex is the premier partner for institutions pioneering DeFi & RWAs. Hong Kong-based since 2016, we turn bold visions into secure, scalable blockchain solutions—driving adoption with unmatched expertise.
Comment on lines 35 to +40
Copy link
Contributor

@coderabbitai coderabbitai bot Dec 8, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Reconsider mandatory verbatim LinkedIn description.

Requiring employees to use identical, verbatim corporate copy in LinkedIn Experience descriptions may:

  1. Violate LinkedIn platform norms (which expect authentic, personal summaries).
  2. Appear inauthentic or spam-like when standardized across employees.
  3. Reduce individual voice and employee engagement with their own professional profiles.

Consider allowing employees to paraphrase the key message while maintaining brand consistency:

- Add Holdex as your current experience in the "Experience" section. Use this
- mandatory description:
-
- > Holdex is the premier partner for institutions pioneering DeFi & RWAs. Hong Kong-based since 2016, we turn bold visions into secure, scalable blockchain solutions—driving adoption with unmatched expertise.
+ Add Holdex as your current experience in the "Experience" section. Your description should highlight:
+ - Your role and contributions at Holdex
+ - Key focus area (e.g., DeFi, RWAs, blockchain solutions)
+ - Optional: Holdex's mission (e.g., "pioneering DeFi & RWAs solutions")
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
### LinkedIn Profile
Must mention Holdex in the ‘Experiences’ tab & place it as the recent / current
role.
Add Holdex as your current experience in the "Experience" section. Use this
mandatory description:
Mandatory `Experience` description:
> Holdex is premier partner for institutions pioneering DeFi & RWAs. Hong Kong-based since 2016, we turn bold visions into secure, scalable blockchain solutions – driving adoption with unmatched expertise.
> Holdex is the premier partner for institutions pioneering DeFi & RWAs. Hong Kong-based since 2016, we turn bold visions into secure, scalable blockchain solutions—driving adoption with unmatched expertise.
### LinkedIn Profile
Add Holdex as your current experience in the "Experience" section. Your description should highlight:
- Your role and contributions at Holdex
- Key focus area (e.g., DeFi, RWAs, blockchain solutions)
- Optional: Holdex's mission (e.g., "pioneering DeFi & RWAs solutions")
🤖 Prompt for AI Agents 
In docs/ADVOCACY.md around lines 35-40, the current text mandates a verbatim
LinkedIn "Experience" description which risks inauthenticity and platform-policy
issues; change the wording to remove the requirement to paste exact copy and
instead require employees to list Holdex as their current employer and role
while allowing paraphrase; provide a short, optional "recommended blurb" that
employees may use or adapt, plus a small set of brand-approved keywords/phrases
to ensure consistency, and add a note linking to brand resources and legal/PR
contact for approvals.

### X (Twitter) Profile

- Must mention your role @HoldexIo within the profile description.
- Link to Holdex website / portfolio.
- Location: localhost
- Description: State your role at @HoldexIo.
- Link: To Holdex website/portfolio.
- Location: localhost.

Engage actively: Share Holdex news/updates, interact with our community, respond
to comments/questions, and tag [@holdexio](https://x.com/holdex.io) and
[@zolotokrylin](https://x.com/zolotokrylin)
Comment on lines +1 to +50
Copy link
Contributor

@coderabbitai coderabbitai bot Dec 8, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Assess overall prescriptiveness and employee autonomy impact.

While the rewrite successfully shifts the advocacy guidelines to a structured, policy-like format (aligning with the PR objective), the cumulative effect of multiple "mandatory" requirements—combined with restrictions (exclusivity clause), unusual specifications ("localhost"), and prescriptive engagement mandates—may create friction with employees and undermine authentic advocacy.

Recommendations:

  • Replace "must/mandatory" language with "should" in non-critical areas to preserve employee autonomy.
  • Allow flexibility for profile attributes that don't directly impact brand messaging (e.g., timezone/location, contact info).
  • Distinguish between hard requirements (e.g., Holdex company affiliation) and aspirational guidance (e.g., engagement on social media).
  • Consider adding a rationale section explaining why each requirement serves the company and employees.

This will maintain strong advocacy positioning while respecting employee agency.

Would you like me to generate a revised version that balances prescriptiveness with employee autonomy?

🤖 Prompt for AI Agents 
In docs/ADVOCACY.md around lines 1–50 the advocacy guidelines are overly
prescriptive (many "must/mandatory" items, exclusivity clause, fixed
placeholders like "localhost") which reduces employee autonomy; revise by
replacing non-critical "must/mandatory" language with "should" or "recommended",
remove or rephrase the exclusivity requirement to allow personal affiliations,
replace hard-coded placeholders (e.g., "localhost") with flexible options like
"your city/region" or "optional", explicitly separate hard requirements (company
affiliation, acceptable conduct) from aspirational guidance (social engagement,
profile phrasing) using clear headings, and add a one-paragraph rationale under
each requirement explaining why it exists and whether it is optional or
required.

5 changes: 2 additions & 3 deletions docs/LEAVE_POLICY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,9 +45,8 @@ leave).

### Reimbursable Leave

1. In case of the agreement termination after the Minimum Service Period,
up to 5 unused Paid Leave days can be compensated
based on the following formula:
1. In case of the agreement termination after the Minimum Service Period, up to
5 unused Paid Leave days can be compensated based on the following formula:

```js
compensation = monthlyRate / 30 * reimbersableDays
Expand Down