<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://handbook.unicis.tech/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="https://handbook.unicis.tech/feed.php">
        <title>Unicis Handbook</title>
        <description></description>
        <link>https://handbook.unicis.tech/</link>
        <image rdf:resource="https://handbook.unicis.tech/_media/wiki/logo.png" />
       <dc:date>2026-06-01T20:27:41+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://handbook.unicis.tech/pub/company/traction?rev=1779688593&amp;do=diff"/>
                <rdf:li rdf:resource="https://handbook.unicis.tech/pub/processes/eu_project_delivery?rev=1779689443&amp;do=diff"/>
                <rdf:li rdf:resource="https://handbook.unicis.tech/pub/development/release?rev=1779211439&amp;do=diff"/>
                <rdf:li rdf:resource="https://handbook.unicis.tech/pub/processes/invoicing_billing?rev=1779688593&amp;do=diff"/>
                <rdf:li rdf:resource="https://handbook.unicis.tech/pub/trust_center/policies/it_security_policy?rev=1728986071&amp;do=diff"/>
                <rdf:li rdf:resource="https://handbook.unicis.tech/pub/company/communications?rev=1742164355&amp;do=diff"/>
                <rdf:li rdf:resource="https://handbook.unicis.tech/pub/development/source_code?rev=1727539180&amp;do=diff"/>
                <rdf:li rdf:resource="https://handbook.unicis.tech/pub/processes/customer_onboarding?rev=1779688593&amp;do=diff"/>
                <rdf:li rdf:resource="https://handbook.unicis.tech/pub/processes/partner_onboarding?rev=1779688593&amp;do=diff"/>
                <rdf:li rdf:resource="https://handbook.unicis.tech/pub/processes/platform_release?rev=1779689296&amp;do=diff"/>
                <rdf:li rdf:resource="https://handbook.unicis.tech/pub/processes/process_template?rev=1779688593&amp;do=diff"/>
                <rdf:li rdf:resource="https://handbook.unicis.tech/pub/processes/start?rev=1779688593&amp;do=diff"/>
                <rdf:li rdf:resource="https://handbook.unicis.tech/pub/processes/support_resolution?rev=1779689632&amp;do=diff"/>
                <rdf:li rdf:resource="https://handbook.unicis.tech/pub/recruitment/open_positions?rev=1753279766&amp;do=diff"/>
                <rdf:li rdf:resource="https://handbook.unicis.tech/pub/trust_center/vendor_questionnaires?rev=1759841069&amp;do=diff"/>
                <rdf:li rdf:resource="https://handbook.unicis.tech/pub/trust_center/policies/privacy_policy?rev=1728986102&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="https://handbook.unicis.tech/_media/wiki/logo.png">
        <title>Unicis Handbook</title>
        <link>https://handbook.unicis.tech/</link>
        <url>https://handbook.unicis.tech/_media/wiki/logo.png</url>
    </image>
    <item rdf:about="https://handbook.unicis.tech/pub/company/traction?rev=1779688593&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-05-25T05:56:33+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Traction: Rocks, Meetings &amp; Issues</title>
        <link>https://handbook.unicis.tech/pub/company/traction?rev=1779688593&amp;do=diff</link>
        <description>Traction: Rocks, Meetings &amp; Issues

Traction is the EOS discipline that turns vision into execution. It is built on three things: Rocks (quarterly priorities), Level 10 Meetings (weekly execution rhythm), and the Issues List (structured problem solving). Without traction, the best strategy stays on paper.</description>
    </item>
    <item rdf:about="https://handbook.unicis.tech/pub/processes/eu_project_delivery?rev=1779689443&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-05-25T06:10:43+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>EU Project Delivery</title>
        <link>https://handbook.unicis.tech/pub/processes/eu_project_delivery?rev=1779689443&amp;do=diff</link>
        <description>EU Project Delivery

← Back to Core Processes

----------

Purpose

To deliver EU-funded project obligations (deliverables, milestones, reporting) on time, with clear internal ownership, and without disrupting core platform work.

Owner

Predrag Tasevski — Stakeholder &amp; EU Projects Management</description>
    </item>
    <item rdf:about="https://handbook.unicis.tech/pub/development/release?rev=1779211439&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-05-19T17:23:59+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Releasing</title>
        <link>https://handbook.unicis.tech/pub/development/release?rev=1779211439&amp;do=diff</link>
        <description>Releasing

Warning

This page is still in progress and may require refinement.

Versioning Scheme

The Unicis Platform uses Calendar Versioning (CalVer):

	*  Major/Minor releases: vYYYY-MM (e.g. v2026-05)
	*  Patch releases: vYYYY-MM-DD (e.g. v2026-05-12)

Release branches follow:</description>
    </item>
    <item rdf:about="https://handbook.unicis.tech/pub/processes/invoicing_billing?rev=1779688593&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-05-25T05:56:33+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Invoicing &amp; Billing</title>
        <link>https://handbook.unicis.tech/pub/processes/invoicing_billing?rev=1779688593&amp;do=diff</link>
        <description>Invoicing &amp; Billing

	&quot; 🔄 Status: Draft — Will be updated when billing.unicis.tech is live.&quot;

← Back to Core Processes

----------

Purpose

To issue invoices accurately, collect payment reliably, and maintain clean financial records — for customers, partners, and EU project claims.</description>
    </item>
    <item rdf:about="https://handbook.unicis.tech/pub/trust_center/policies/it_security_policy?rev=1728986071&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-10-15T09:54:31+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>IT Security Policy</title>
        <link>https://handbook.unicis.tech/pub/trust_center/policies/it_security_policy?rev=1728986071&amp;do=diff</link>
        <description>IT Security Policy

Effective date: 17.05.2024.

Security is very important to Unicis and everyone here is doing their best to keep your presentations and data secure. This document describes our internal security policies, and minimum security baseline and how those translate into creating a secure platform, add-ons and plugins that you can trust.</description>
    </item>
    <item rdf:about="https://handbook.unicis.tech/pub/company/communications?rev=1742164355&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-03-16T22:32:35+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Communications</title>
        <link>https://handbook.unicis.tech/pub/company/communications?rev=1742164355&amp;do=diff</link>
        <description>Communications

This page explains what every team member (Unicians) needs to know in order to effectively contribute at Unicis.

All hands

Unicis organizes a meeting called the “All hands” every month. All team members, both internal and external, are required to attend the monthly “All Hands” meeting. All meetings are recorded and team members who can’t attend should watch the recording within a few days.</description>
    </item>
    <item rdf:about="https://handbook.unicis.tech/pub/development/source_code?rev=1727539180&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-09-28T15:59:40+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Source Code</title>
        <link>https://handbook.unicis.tech/pub/development/source_code?rev=1727539180&amp;do=diff</link>
        <description>Source Code

 Warring

The content of this page is still in progress and needs some tweaking.

Introduction

Welcome to the Unicis Source Code Handbook. This guide provides an overview of how we manage our source code across different repositories, both private and public. It covers the structure, guidelines, and best practices for contributing to the Unicis Platform.</description>
    </item>
    <item rdf:about="https://handbook.unicis.tech/pub/processes/customer_onboarding?rev=1779688593&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-05-25T05:56:33+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Customer Onboarding</title>
        <link>https://handbook.unicis.tech/pub/processes/customer_onboarding?rev=1779688593&amp;do=diff</link>
        <description>Customer Onboarding

← Back to Core Processes

----------

Purpose

To take a new trial signup from first contact to an active, value-realising customer — consistently, within 14 days of signup.

Owner

Predrag Tasevski — CEO / Visionary

Trigger

This process starts when a new trial signup is confirmed — either via the unicis.tech signup form (Mautic notification) or via a direct outreach that results in a trial account being created.</description>
    </item>
    <item rdf:about="https://handbook.unicis.tech/pub/processes/partner_onboarding?rev=1779688593&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-05-25T05:56:33+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Partner Onboarding</title>
        <link>https://handbook.unicis.tech/pub/processes/partner_onboarding?rev=1779688593&amp;do=diff</link>
        <description>Partner Onboarding

	&quot; 🔄 Status: Draft — This process is defined but not yet fully operational. billing.unicis.tech and the partner programme are in development. Update this page when the partner programme launches.&quot;

← Back to Core Processes

----------

Purpose

To onboard new reseller, integration, or referral partners into the Unicis partner programme — from first contact to active, contracted, and billing-enabled partner.</description>
    </item>
    <item rdf:about="https://handbook.unicis.tech/pub/processes/platform_release?rev=1779689296&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-05-25T06:08:16+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Platform Release</title>
        <link>https://handbook.unicis.tech/pub/processes/platform_release?rev=1779689296&amp;do=diff</link>
        <description>Platform Release

← Back to Core Processes

----------

Purpose

To ship Unicis Platform releases consistently, with clear quality gates, predictable communication, and no surprises for customers or the community.

Owner

Peter Zlatev — CTO

Trigger

This process starts when the team agrees a set of features/fixes is ready to ship — either at the end of a planned sprint or when a critical fix requires an unplanned release.</description>
    </item>
    <item rdf:about="https://handbook.unicis.tech/pub/processes/process_template?rev=1779688593&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-05-25T05:56:33+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Process Template</title>
        <link>https://handbook.unicis.tech/pub/processes/process_template?rev=1779688593&amp;do=diff</link>
        <description>Process Template

Copy this page when creating a new Core Process. Replace all placeholder text in [brackets].

← Back to Core Processes

----------

[Process Name]

Purpose

[Why does this process exist? What problem does it solve? One or two sentences.]

Owner

[Full name]</description>
    </item>
    <item rdf:about="https://handbook.unicis.tech/pub/processes/start?rev=1779688593&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-05-25T05:56:33+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Core Processes</title>
        <link>https://handbook.unicis.tech/pub/processes/start?rev=1779688593&amp;do=diff</link>
        <description>Core Processes

This section documents the Core Processes that run Unicis. A Core Process is a named, repeatable workflow that produces a consistent result. Every process has a single owner, a clear set of steps, and a list of the tools involved.

Documenting processes is not bureaucracy — it is how Unicis delivers consistent quality as the team grows, onboards new Unicians, and operates across time zones.</description>
    </item>
    <item rdf:about="https://handbook.unicis.tech/pub/processes/support_resolution?rev=1779689632&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-05-25T06:13:52+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Support Resolution</title>
        <link>https://handbook.unicis.tech/pub/processes/support_resolution?rev=1779689632&amp;do=diff</link>
        <description>Support Resolution

	&quot; 🔄 Status: Draft — Review and approve at next Quarterly Session.&quot;

← Back to Core Processes

----------

Purpose

To resolve customer and community support requests consistently, with clear response time expectations and a closed feedback loop.

Owner</description>
    </item>
    <item rdf:about="https://handbook.unicis.tech/pub/recruitment/open_positions?rev=1753279766&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-07-23T14:09:26+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Unicis Open Positions</title>
        <link>https://handbook.unicis.tech/pub/recruitment/open_positions?rev=1753279766&amp;do=diff</link>
        <description>Unicis Open Positions

All open hiring positions at Unicis can be found here.

job hiring job position

Internship

Unicis is building a cutting-edge Security Operations Center (SOC) using an open-source technology stack. We are looking for an experienced SOC Engineer who has hands-on experience in setting up and managing a SOC using open-source tools such as Zabbix, Wazuh, and MISP, containerized with Docker.</description>
    </item>
    <item rdf:about="https://handbook.unicis.tech/pub/trust_center/vendor_questionnaires?rev=1759841069&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-10-07T12:44:29+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Vendor Questionnaires</title>
        <link>https://handbook.unicis.tech/pub/trust_center/vendor_questionnaires?rev=1759841069&amp;do=diff</link>
        <description>Vendor Questionnaires

Unicis vendor questionnaire is based on MVSP controls and provides a clear set of requirements for enterprise-ready products and services.

 Please answer each question with a “yes” or “no”, and provide a brief description of the process or controls in place if the answer is</description>
    </item>
    <item rdf:about="https://handbook.unicis.tech/pub/trust_center/policies/privacy_policy?rev=1728986102&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-10-15T09:55:02+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Privacy Policy</title>
        <link>https://handbook.unicis.tech/pub/trust_center/policies/privacy_policy?rev=1728986102&amp;do=diff</link>
        <description>Privacy Policy

Effective date: 01.03.2024.

This privacy policy will explain how we do not use the personal data and that we do not collect any data from you when you use our website.

Topics:

What data do we collect?

 We do not collect any data from you.</description>
    </item>
</rdf:RDF>
