Results for “register”

Conduct a defensible cybersecurity risk assessment using the NIST SP 800-30 Rev 1 methodology: prepare scope and a risk model, identify threat sources and threat events, identify vulnerabilities and predisposing conditions, determine likelihood and impact, compute risk, and communicate results as a prioritized risk register. Use when an organization needs an actual risk *assessment* (not a maturity score), when a control framework (CSF, ISO 27001, RMF, SOC 2, PCI) requires a documented risk analysis as input, when leadership asks "what are our top risks and how bad are they", when assessing risk for a new system or major change, or when building a risk register from scratch. This is the methodology that feeds framework selection, ATO packages, and treatment decisions. Keywords: risk assessment, NIST 800-30, threat modeling, likelihood and impact, risk register, risk analysis, threat sources, vulnerabilities, risk determination, qualitative risk, risk matrix, residual risk, risk treatment.

The English summary is being prepared. Showing the original description.

Checks a master document register extract for gaps and returns a DRAFT question list for document control: missing or out-of-sequence revisions, overdue or slipping deliverables, numbering that breaks the project convention, duplicates and incomplete rows, each with row, test and quoted evidence. Never edits the register, re-baselines a date or marks a deliverable complete. Use when the user asks to "check the MDR", "find the gaps in the deliverables list" or "prepare questions on the drawing register". Do not use for drafting a transmittal from a document list, use transmittal-drafter instead. Drafts for human review; never approves, authorises or signs off.

The English summary is being prepared. Showing the original description.

Builds a DRAFT interface register between disciplines or parties from meeting notes, action lists and drawings or document lists: one row per interface with the requesting and providing party, the information needed, the related document number, the need-by date with its source, the status as minuted and a quoted source, plus UNKNOWN and questions where the notes are silent. Never sets a date, rates priority, assigns ownership beyond what the notes state or closes an interface. Use when the user asks to "build an interface register from these minutes", "list the interfaces between piping and civil", "who owes what to whom on this package", "update the interface register from this week's meeting" or "turn these action items into an interface list". Do not use for recording a design or document change raised in a meeting, use management-of-change-intake instead. Drafts for human review; never approves, authorises or signs off.

The English summary is being prepared. Showing the original description.

Register a Snowflake table or view as a Narrative dataset from SQL, with no Configuration screen and no browser. Not for installing or configuring the native app, and not for querying a dataset that already exists. Use when: "register this table as a dataset", "register a Snowflake dataset from SQL", "onboard my_table to Narrative", "script dataset registration", "add this view to my data plane". (narrative-common)

The English summary is being prepared. Showing the original description.

Adds a per-form settings panel to the JetFormBuilder Gutenberg form editor sidebar — registers REST-exposed post meta on the form CPT, enqueues a block-editor JS bundle, and registers a panel via the JFB-specific 'jet.fb.register.plugins' filter using @wordpress/components (TextControl, SelectControl, ToggleControl) and JFB's useMetaState hook for two-way binding to post meta. Use when a companion plugin needs settings that vary per form (e.g. upload folder, file size limit, integration target) instead of (or in addition to) site-wide defaults from the global Settings page. Triggers on mentions of "JFB form sidebar", "JFB form settings panel", "form-level settings", "useMetaState", "jet.fb.register.plugins", "jet-form-builder/editor-assets/before", or scaffolding a JFB companion plugin that needs per-form config.

The English summary is being prepared. Showing the original description.

Register a custom Query type for JetEngine's Query Builder — extend \Jet_Engine\Query_Builder\Queries\Base_Query for the runtime query class, extend \Jet_Engine\Query_Builder\Query_Editor\Base_Query for the editor component, then hook BOTH register actions — jet-engine/query-builder/queries/register (factory) for the runtime, jet-engine/query-builder/query-editor/register for the editor UI. Five abstract methods on Base_Query — _get_items(), get_items_total_count(), get_items_page_count(), get_items_pages_count(), get_current_items_page(). Built-in cache via get_cached_data() / update_query_cache(). Custom queries participate in JE 3.8+ MCP tool exposure and the frontend query inspector automatically. Use when scaffolding a custom query type (HPOS WC orders, third-party API source, custom DB table) for JetEngine listings, dynamic widgets, or REST API endpoints.

The English summary is being prepared. Showing the original description.

Scaffolds and reviews custom WordPress REST API endpoints registered via register_rest_route on rest_api_init — namespace and version slug, permission_callback authorization (NEVER __return_true on state-changing routes, which is the most common plugin-side vulnerability on wp.org), args schema with validate_callback / sanitize_callback / type / enum, object-level capability checks via current_user_can with object ID, responses with WP_REST_Response and WP_Error carrying an HTTP status, no raw DB rows / sensitive columns in responses, cookie auth via X-WP-Nonce, REST vs admin-ajax decision. Recommends the better-route library when the plugin grows past a few endpoints. Use when scaffolding or reviewing a REST endpoint, or migrating from admin-ajax. Triggers on register_rest_route, rest_api_init, permission_callback, WP_REST_Request, WP_REST_Response, WP_Error, X-WP-Nonce, rest_ensure_response, register_rest_field, or any file path containing /rest/ or /api/ in a WP plugin or theme.

The English summary is being prepared. Showing the original description.

Scaffolds and reviews the main entry-point PHP file of a WordPress plugin — header (with Requires Plugins for WP 6.5+), ABSPATH guard, file/path/url/version constants, Composer + PSR-4 with manual spl_autoload_register fallback, register_activation_hook requirements check, Plugin class instantiation on plugins_loaded, and the WP 6.7+ rule that translation functions must not trigger before after_setup_theme. Use when scaffolding a new plugin or reviewing its main file. Triggers on Plugin Name headers, register_activation_hook, Requires Plugins, spl_autoload_register, plugins_loaded, or composer.json at the plugin root.

The English summary is being prepared. Showing the original description.

Register a custom Listings callback for JetEngine — the per-field transform fired when a Dynamic Field widget renders meta values (Format date, Format number, Get post title, Convert units, …). Two registration paths are supported. Legacy 3-filter via jet-engine/listings/allowed-callbacks (label), jet-engine/listings/allowed-callbacks-args (control schema), and jet-engine/listing/dynamic-field/callback-args (positional args at runtime). Modern single-call $manager->register_callback($name, $label, $args) hooked on jet-engine/callbacks/register fires the three filters internally for you. Critical contract — the callback identifier you register MUST be a real PHP callable string (a global function name OR `Fully\\Qualified\\Class::method`). Bare static method names like `'unit_converter'` fail JE's is_callable() gate at apply_callback() and the rendered field silently becomes empty. Use when scaffolding a JetEngine companion plugin's listing-field transform, when seeing "callback appl...

The English summary is being prepared. Showing the original description.

Set up gbrain so a coding agent can call it. Install its command-line tool, initialize a local PGLite or Supabase brain, register MCP, the agent connection mechanism, and record trust policies for each remote.

• Setting up gbrain on a machine for the first time
• Initializing a local PGLite brain
• Configuring a Supabase brain

Set up ruvector@0.3.3 with supporting packages, register its MCP server for agent access, and verify installation with diagnostic commands and smoke tests. Helps prepare the dependencies needed for initial use of /vector subcommands.

• Setting up ruvector for the first time
• Resolving missing dependencies for Brain, SONA, or LLM commands
• Registering the ruvector MCP server with Claude

Find background music, sound effects, images, and icons from existing assets, shared caches, or HeyGen. Save selected files locally and register them in an inventory, giving the agent a usable file path.

• Finding background music and sound effects for a video
• Sourcing background images and icons
• Registering existing assets in an inventory

Define the types and shared registrations needed to add a syncable entity to Twenty's server. Set up database entities, editable fields, action types, and relationships as the foundation for workspace migration implementation.

• Define a new syncable entity in Twenty
• Create flat data and migration action types
• Register editable fields and comparison rules

Build and operate bioinformatics workflows on Latch using Python, Nextflow, or Snakemake. Configure computing resources and input forms, move data, connect Registry records, and register, debug, launch, and monitor analysis runs.

• Create and register Python analysis workflows
• Package Nextflow or Snakemake pipelines for Latch
• Connect Latch Data and Registry records

Plan a practical equipment register for tracking serial numbers, assignees, locations, purchase values, warranties, and returns. On request, create empty CSV templates, SQL table definitions, JSON Schema, or Notion mappings from a shared field list.

• Setting up a laptop and equipment register
• Planning equipment returns when employees leave
• Reviewing fields needed for an asset audit

Plan a simple daily attendance register covering check-in, check-out, hours, absences, and correction requests. When requested, generate empty templates in CSV, SQL, JSON Schema, or Notion mappings to prepare records for payroll input.

• Designing a daily check-in and check-out register
• Clarifying late arrival and half-day recording rules
• Creating empty attendance templates for payroll input

Captures screenshots on registered computers and manages saved captures. Supports screen recording on macOS and timed screenshot sequences on HarmonyOS, checking available capabilities first and returning the finalized file path when recording stops.

• Capturing screenshots on a registered computer
• Recording a display or selected region on macOS
• Saving timed screenshot sequences on HarmonyOS

Identify risks in projects, vendors, processes, and decisions, then rank them by likelihood and impact. Produce a prioritized risk register, a structured list of risks with practical mitigation actions, responsible owners, and current status.

• Assessing risks before starting a project
• Reviewing risks associated with a vendor
• Identifying potential failures in business processes

Find and organize technical debt, the code issues deferred for later improvement. Maintain a register, rank items by impact and repair effort, and report unresolved work and changes over each sprint.

• Scan code for signs of deferred maintenance
• Record known issues and reasons for deferring fixes
• Prioritize fixes by impact and effort

Manage machine learning models and their versions in the Agent Platform Model Registry. List registered models, inspect details, upload new versions, update names or descriptions, and delete models through workflows that require confirmation for changes.

• List registered models and inspect their details
• Register a new model or model version
• Update a model's display name or description

Map sensitive data across the systems you manage, explore what a compromised asset could expose, and maintain a risk register. Record likelihood, impact, owners, mitigations, and review dates to support ongoing security planning.

• Locating sensitive data across managed systems
• Assessing the impact of a compromised server or worker
• Recording risk owners, mitigations, and review dates

Import an FBX character into a CARLA source build as a pedestrian available through the Python API. Check its GEN3 skeleton, create assets and a walker blueprint, register it, and verify spawning, ground placement, and movement.

• Add a custom FBX character as a CARLA pedestrian
• Check whether an FBX uses the required GEN3 skeleton
• Investigate floating or motionless imported pedestrians

Maintain a register of trademarks, patents, domains, and other intellectual property. Produce deadline reports, add assets, record maintenance updates, and audit missing dates or inconsistent ownership records, using supplied data or a connected IP management system.

• Listing intellectual property deadlines for the next 90 days
• Adding newly registered trademarks or granted patents
• Recording completed maintenance filings and payments

Build an AI system register for EU AI Act reviews. Track owners, deployment status, EU connections, and each system’s role and risk category through a guided discussion, preserving classification reasons and dates for future review.

• Register AI systems used or planned across an organization
• Review each system’s role and risk category
• Find systems approaching their next review date