You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
159 lines
5.5 KiB
HTML
159 lines
5.5 KiB
HTML
<?xml version="1.0" encoding="utf-8"?>
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
|
|
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
|
|
<html xmlns="http://www.w3.org/1999/xhtml">
|
|
<head>
|
|
<title> CACert -- Nucleus Assurance Policy </title>
|
|
<style type="text/css">
|
|
<!--
|
|
.q {
|
|
color : green;
|
|
text-indent : 2em;
|
|
font-weight: bold;
|
|
font-style:italic;
|
|
}
|
|
.error {
|
|
color : red;
|
|
font-weight: bold;
|
|
text-align: center;
|
|
font-style:italic;
|
|
}
|
|
.change {
|
|
color : blue;
|
|
font-weight: bold;
|
|
}
|
|
-->
|
|
</style>
|
|
|
|
</head>
|
|
|
|
<body>
|
|
<h1> Nucleus Assurance Policy </h1>
|
|
|
|
<table width="100%">
|
|
<tr>
|
|
<td>
|
|
Editor: Ulrich<br />
|
|
Creation Date : 2013-03-24<br />
|
|
Status: WIP <br />
|
|
Licence: <a style="color: steelblue" href="https://wiki.cacert.org/Policy#Licence" title="this document is Copyright © CAcert Inc., licensed openly under CC-by-sa with all disputes resolved under DRP. More at wiki.cacert.org/Policy" > CC-by-sa+DRP </a><br />
|
|
</td><td align="right">
|
|
<a href="https://www.cacert.org/policy/PolicyOnPolicy.html"><img src="images/cacert-wip.png" alt="CAcert Policy Status - Work In Progress" height="31" width="88" style="border-style: none;" /></a>
|
|
</td>
|
|
</tr>
|
|
</table>
|
|
|
|
<h2 id="s0"> 0. Preliminaries </h2>
|
|
|
|
<p id="s0.1"> <b> 0.1 Introduction. </b>
|
|
This sub-policy extends the
|
|
<a href="https://www.cacert.org/policy/AssurancePolicy.html">
|
|
Assurance Policy</a> ("AP" => COD13)
|
|
by specifying how a party of candidate Assurers can be led by a Senior Assurer
|
|
to self-Assure themselves up to Assurer status.
|
|
</p>
|
|
|
|
<p id="s0.2"><b> 0.2 Scope and Authority. </b>
|
|
This policy is a subsidiary policy under Assurance Policy (AP).
|
|
This policy applies to all Members of the CAcert Community.
|
|
</p>
|
|
|
|
<h3 id="s0.3"> 0.3 Terms.</h3>
|
|
|
|
<ul>
|
|
<li> Candidate Assurer (or candidate) is a Member of CAcert who attends
|
|
a Nucleus Event with the intention of reaching Assurer at that event.</li>
|
|
<li>
|
|
A quorum consists of sufficient Assurers and Members (candidates)
|
|
such that the sum of allocatable points
|
|
to each candidate can reach 100 Assurance Points,
|
|
assuming that candidates are deemed
|
|
Assurers (with zero Experience Points),
|
|
and,
|
|
contribute their 10 Assurance Points to the mix.</li>
|
|
<li>
|
|
Senior Assurer is a status and term defined
|
|
by AO from time to time.</li>
|
|
</ul>
|
|
|
|
<h2 id="s2"> 2. The Nucleus Event </h2>
|
|
<p id="s2.1"><b> 2.1 </b>
|
|
A Nucleus event is a training and assurance event that brings many candidate
|
|
Assurers up to the level of Assurer in one event, by allocating
|
|
the Assurance Points that they would be able to allocate, in advance.
|
|
</p>
|
|
|
|
<p id="s2.2"><b> 2.2 </b>
|
|
A Nucleus event should be led by a Senior Assurer,
|
|
and should be assisted by at least one other Assurer.
|
|
The 4 eyes principle must be maintained.
|
|
</p>
|
|
|
|
<p id="s2.3"><b> 2.3 </b>
|
|
A Nucleus event should be proposed to Assurance Officer,
|
|
who will provide blessing and assistance in adding the
|
|
borrowed points.
|
|
</p>
|
|
<ul>
|
|
<li>Leader, status and points available.</li>
|
|
<li>Assisting Assurer(s), status and points available.</li>
|
|
<li>Description and quantity of Candidates.</li>
|
|
<li>Calculation of points showing that a quorum will be present.</li>
|
|
<li>Proposed training programme.</li>
|
|
</ul>
|
|
|
|
<p class="q">Note that this above clause does not give the AO the power to
|
|
stop or modify the activity. Such responsibility is left
|
|
entirely with the Senior Asssurer.
|
|
The policy should seek to be self-maintaining and efficiently
|
|
distributable, so putting the AO in as a blocking step would
|
|
not be appropriate to that goal. </p>
|
|
|
|
<p id="s2.4"><b> 2.4 </b>
|
|
On the day, a quorum of Assurers and candidates must be found
|
|
(as present and working).
|
|
If the quorum fails, Assurances by the candidates are invalid.
|
|
</p>
|
|
|
|
<p id="s2.5"><b> 2.5 </b>
|
|
After the event, the Leader must submit a report to AO.
|
|
Notification and summary information should be provided to Board,
|
|
and included in the AO's annual report to AGM.
|
|
</p>
|
|
|
|
<p id="s2.6"><b> 2.6 </b>
|
|
The Assurance Handbook (<a href="https://wiki.cacert.org/AssuranceHandbook2">AH</a>) should describe the process and detail of the Nucleus event.
|
|
</p>
|
|
|
|
<h2 id="s3"> 3. Ephemeral Points </h2>
|
|
<p id="s3.1"><b> 3.1 </b>
|
|
If there is a quorum of candidate Assurers such that
|
|
if they were to be Assurers, their allocated Assurance Points
|
|
to each other would confirm their status as Assurer,
|
|
if so allocatable.
|
|
To fold time such that these points are allocatable before
|
|
ordinarily approved under the basic mechanisms of AP,
|
|
the points must be borrowed from somewhere.
|
|
The points may be borrowed by any mechanism
|
|
as directed by the Assurance Officer from time to time.
|
|
</p>
|
|
|
|
<p id="s3.2"><b> 3.2 </b>
|
|
In the longer term, a change should be put into the system
|
|
such that the borrowed points may be directly allocated
|
|
and tracked for normal governance purposes.
|
|
</p>
|
|
|
|
<p id="s3.3"><b> 3.3 </b>
|
|
The borrowed points are returned after each candidate is
|
|
confirmed as Assurer.
|
|
</p>
|
|
|
|
<p id="s3.4"><b> 3.4 </b>
|
|
The use of borrowed points and the absence of any system feature
|
|
does not remove the duty of each Assurer under AP.
|
|
</p>
|
|
|
|
</body>
|
|
</html>
|