Kin Lane kinlane

Create Account → Open checking, savings, or loan accounts
Create Form Submission → KYC/AML questionnaires
Upload File/Create Asset → ID documents, proof of address
Create Extraction Task → OCR on identity documents
Create Data Source Query → Pull credit bureau data, sanctions lists, PEP screening
Create Moderation Report → Flag high-risk customers
Complete Workflow Step → Multi-level approval for high-value accounts
Send Transactional Email → Welcome kit, account details

	[
	{
	"name": "AI",
	"ring": "Established",
	"quadrant": "Concepts",
	"isNew": "TRUE",
	"description": "A branch of computer science focused on creating systems capable of performing tasks that typically require human intelligence, such as learning, reasoning, problem-solving, perception, and language understanding. It is a foundational component in modern data architectures and enterprise data management practices."
	},
	{
	"name": "EDI",

	[
	{
	"name": "Path-to-production mapping",
	"ring": "Optimizing",
	"quadrant": "Concepts",
	"isNew": "TRUE",
	"description": "<p>Although <strong>path-to-production mapping</strong> has been a near-universal practice at Thoughtworks since codifying <em><a href=\"https://www.amazon.com/Continuous-Delivery-Deployment-Automation-Addison-Wesley/dp/0321601912\">Continuous Delivery</a></em>, we often come across organizations unfamiliar with the practice. The activity is most often done in a workshop with a cross-functional group of people — that includes everyone involved in designing, developing, releasing and operating the software — around a shared whiteboard (or virtual equivalent). First, the steps in the process are listed in order, from the developer workstation all the way to production. Then, a facilitated session is used to capture further information and pain points. The most common technique we see is based on <a href=\"https://en.wikipedia.org/wiki/Value-stream_mapping\">value-stream

	[
	{
	"name": "Path-to-production mapping",
	"ring": "Optimizing",
	"quadrant": "Concepts",
	"isNew": "TRUE",
	"description": "<p>Although <strong>path-to-production mapping</strong> has been a near-universal practice at Thoughtworks since codifying <em><a href=\"https://www.amazon.com/Continuous-Delivery-Deployment-Automation-Addison-Wesley/dp/0321601912\">Continuous Delivery</a></em>, we often come across organizations unfamiliar with the practice. The activity is most often done in a workshop with a cross-functional group of people — that includes everyone involved in designing, developing, releasing and operating the software — around a shared whiteboard (or virtual equivalent). First, the steps in the process are listed in order, from the developer workstation all the way to production. Then, a facilitated session is used to capture further information and pain points. The most common technique we see is based on <a href=\"https://en.wikipedia.org/wiki/Value-stream_mapping\">value-stream

	[
	{
	"name": "Path-to-production mapping",
	"ring": "Adopt",
	"quadrant": "Techniques",
	"isNew": "TRUE",
	"description": "<p>Although <strong>path-to-production mapping</strong> has been a near-universal practice at Thoughtworks since codifying <em><a href=\"https://www.amazon.com/Continuous-Delivery-Deployment-Automation-Addison-Wesley/dp/0321601912\">Continuous Delivery</a></em>, we often come across organizations unfamiliar with the practice. The activity is most often done in a workshop with a cross-functional group of people — that includes everyone involved in designing, developing, releasing and operating the software — around a shared whiteboard (or virtual equivalent). First, the steps in the process are listed in order, from the developer workstation all the way to production. Then, a facilitated session is used to capture further information and pain points. The most common technique we see is based on <a href=\"https://en.wikipedia.org/wiki/Value-stream_mapping\">value-stream ma

	- type: Roles
	data:

	# ===================
	# TECH GROUP
	# ===================
	- name: Mobile App Developer
	description: Creates, designs and develops mobile apps
	domain: Tech
	operations:

	name,ring,quadrant,isNew,status,description
	Continuous compliance,Adopt,Techniques,FALSE,moved in,"<p><strong>Continuous compliance</strong> is the practice of ensuring that software development processes and technologies meet regulatory and security standards on an ongoing basis through automation. Manual compliance checks can slow development and introduce human error, whereas automated checks and audits provide faster feedback, clearer evidence and simplified reporting. </p>
	<p>By integrating <a href=""/radar/techniques/security-policy-as-code"">policy-as-code</a> tools such as <a href=""/radar/tools/open-policy-agent-opa"">Open Policy Agent</a> and generating <a href=""/radar/techniques/software-bill-of-materials"">SBOMs</a> within CD pipelines — aligned with <a href=""/radar/techniques/slsa"">SLSA</a> guidance — teams can detect and address compliance issues early. Codifying rules and best practices enforces standards consistently across teams without creating bottlenecks. <a href=""/radar/languages/open

	- type: Operations
	data:

	# Access Control
	- Add User Access Restrictions
	- Get Users With Access To Protected Branch
	- Remove User Access Restrictions
	- Set User Access Restrictions

	# Access Control Rules